This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Brackets "grey screens" and crashes when editing JS files #7514
Description
Using sprint 38 experimental build 0.38.0-12606 (release 4df8afd) (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.
Activity
rajatrocks commentedon Apr 15, 2014
btw - there are NO extensions installed.
flavioxavier commentedon Apr 18, 2014
Same problem here on linux
redmunds commentedon Apr 18, 2014
@rajatrocks @flavioxavier Start by looking through the Troubleshooting Guide, especially the Brackets is Running Slow section.
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?
dangoor commentedon Apr 21, 2014
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)
matthewoates commentedon Nov 13, 2014
I had this same issue editing a markdown file with live markdown preview.
matthewoates commentedon Nov 13, 2014
Crashed 3 times in 15 minutes.
peterflynn commentedon Nov 13, 2014
@dangoor Any objection to closing this now that JS Code Hints has crash prevention (as of 0.42, late July)?
@rajatrocks @flavioxavier Please let us know if you're still experiencing any crash issues like this. If you are, please gather a crash log and post a link to that issue so we can keep investigating. Otherwise I think we'll close this under the assumption that it was fixed in version 0.42.
matthewoates commentedon Nov 13, 2014
Similar issue here: #9926
dangoor commentedon Nov 17, 2014
Closing per @peterflynn's comment.
@rajatrocks Please reopen if you're still encountering this problem. Thanks!