-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Brackets "grey screens" and crashes when editing JS files #6763
Comments
Comment by rajatrocks btw - there are NO extensions installed. |
Comment by flavioxavier Same problem here on linux |
Comment by redmunds
Use Debug > Reload Without Extensions to make sure an extension is not causing a problem. Does it happen on every single JS file, or only certain ones? Can you post a sample for us to try? Using File > Open Folder... sets the "project" that Brackets uses for searching for relevant code for code hints. What do you have it set to? Try selecting a smaller folder to reduce the scope. Does it happen when just opening a JS file, or when you do certain operations? |
Comment by dangoor reviewed medium to me on the assumption that this is code hints (we'll review again if this does not appear to be code hints) |
Comment by matthewoates I had this same issue editing a markdown file with live markdown preview. |
Comment by matthewoates Crashed 3 times in 15 minutes. |
Comment by peterflynn
|
Comment by matthewoates Similar issue here: adobe/brackets#9926 |
Comment by dangoor Closing per
|
Issue by rajatrocks
Tuesday Apr 15, 2014 at 05:15 GMT
Originally opened as adobe/brackets#7514
Using sprint 38 experimental build 0.38.0-12606 (release 4df8afdad) (and sprint 37 as well) on Mac OSX v10.9.2 Build 13C64, Processor 1.8 GHz intel Core i7, 4 GB 1333 MHz DDR3 memory.
Editing JS file. Brackets Helper uses increasing amounts of CPU until my fan starts and then somewhere over 100%, Brackets crashes. The only way to make it quit is to right-click on the dock icon and choose quit from there.
The text was updated successfully, but these errors were encountered: