White screen when starting Brackets

[eobet]

I just tried Brackets Sprint 31 and 30 on OS X 10.7.5 and all I got was white screens.

Going back to Sprint 26 which is the last one I used still worked though, so now I'm back to that.

Somewhere between 26 and 30 someone messed something up because nothing gets drawn. The cursor does change and I think I managed to highlight some text despite everything being white (because there was a highlight when I got back to 26) so it's not frozen. It just doesn't draw anything.

[JeffryBooher]

@eobet can you attach a screen grab? In our experience this is due to a crash in CEF so you should not see a cursor or any text.

[eobet]

Well, it's just a white empty standard OS X window that shows up, nothing that would look anything special in a screenshot.

Are there any logs or debug info I could attach somehow instead?

[peterflynn]

@eobet It might also be worth trying to do more of a "deep clean" reinstall: delete the old .app from /Applications, empty trash, delete your Brackets cache folder and extensions folder, then download and install a new .app. I'm not super confident that will fix the problem but it's worth a shot.

If you're still seeing it, can you open Activity Monitor and just confirm which Brackets-related processes are running? Normally, you should see four processes -- Brackets, Brackets-node, and two named Brackets-helper. Are there less in your case?

[njx]

Medium priority to @JeffryBooher to track to see if we get more info from the filer.

[eobet]

Deleting the cef_data folder made contents appear again! Thank you for the solution.

Perhaps Brackets should automatically clear this folder if you jump too many versions between updates like I did?

[dangoor]

Removing the tracking label. We need to decide if we're going to do anything more here.

[njx]

Sounds like we should just close this for now. If we heard a lot of examples of bad cache data we would investigate it, but I don't think we've heard a lot of these cases.

[JeffryBooher]

Yep. Closing as per @njx suggested

[ingalls]

This issue is still be kicking around. Just encountered it twice today. As per above, clearing cef_data fixes the problem.

@JeffryBooher @njx @dangoor

[dangoor]

@ingalls I'd suggest opening up a fresh issue. There's a big difference between releases 31 and 40.