New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pygments issue with Objective-J Cappuccino #2215
Comments
Is it this file? https://github.com/cappuccino/cappuccino/blob/master/AppKit/Platform/DOM/CPPlatform.j I can't reproduce this. After downloading it, |
The culprit is When I run pygmentize cappuccino/AppKit/Platform/DOM/CPPlatformPasteboard.j with pygments 2.13.0 on a MacBook Pro 2015 with macOS 12.5.1 and Python 3.9.13, it keeps running for minutes with 1 CPU maxed out. When I eventually press Control-C, the output is:
|
Confirmed, I can replicate that
maxes out a CPU until interrupted. Anybody have an idea about what goes wrong here? |
For the record: I checked the hexdump of the line where it seems to get stuck (according to the stack trace above), but could not see anything unusual or kinky.
|
I have opened #2225 to address this issue. It does not fully fixes the problem, as the lexer seems not to recognize |
We are trying to run pygount which uses pygments and we are having an issue running a small script in which we loop over GitHub repos to extract the lines of codes with pygount.
Looping through repos has worked well for all our repos but for ‘cappuccino.’ Cappuccino has its own language, Objective-J, and we suspected that may be an issue for pygount. The Pygount Repo owner who tested pygount for cappuccino confirmed our suspicion and points towards issues with pygments: "When executing pygount for cappuccino it seems that pygments' Objective-J readings are very slow even with small files and eventually pygments ends up in an infinite loop on the file cappuccino/AppKit/Platform/DOM/CPPlatformPasteboard.j. The same happens when you pass this to the "pygmentize" command line tool from pygments."
We are hoping that you can help us with this issue.
The text was updated successfully, but these errors were encountered: