Grey/White screen crash when editing markdown files with live preview

[matthewoates]

Similar issue to the one described here:
#7025
#7514

The first two logs are from editing markdown files (no JS files were in the working folder) and I don't remember what I was editing for the other two. The first two logs happened within a few minutes of each other.

OS: OSX Yosemite 10.10

Brackets version:
Release 1.0 build 1.0.0-15191 (release 3f2eb90)
build timestamp: Fri Oct 31 2014 14:26:26 GMT-0700

Logs: https://gist.github.com/matthewoates/398804a9a5ec109f4f44

[peterflynn]

Hmm, all these crashes are in a web worker thread... the only thing that uses web workers in Brackets core is JS code hints. Do you have any extensions installed? If so, does the crash still happen if you do Debug > Reload Without Extensions?

[peterflynn]

@JeffryBooher could you take a stab at symbolizing the stack traces?

[matthewoates]

Can the JS Hint extension still crash the editor if I'm not editing any JS files? I'll use it for a little while without extensions to see if I can get it to crash.

Installed extensions:
Brackets Git
Brackets TSLint
Brackets TypeScript
Fonts
LESSHints
Markdown Preview
Toggle Toolbar
Wombatish

[peterflynn]

If some of the crashes happened in folders that didn't contain any JS files (which I think you said was the case for 2 of the crashes?), then the JS code hints worker shouldn't be active at all. (Unless you had opened a JS file earlier in the same session -- it's possible if the JS worker got in a bad state it would just stay running even after switching projects). But the JS worker has pretty strict limits on it now, so it seems a bit unlikely that it's involved.

I'm pretty sure some of the TypeScript extensions use worker threads too though, so definitely try Reload Without Extensions.

[matthewoates]

Yes, there were no JS files for the first two crashes. I was not editing JS files earlier in the sessions.

[JeffryBooher]

@peterflynn it looks like the stack is already symbolized and that NotifyBrowserOfPluginHideWindow is jumping to a rogue function address.

Thread 10 Crashed:: WebCore: Worker
0   libcef.dylib                    0x01aaab9d mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 14388989
1   libcef.dylib                    0x0201692b _CTFontManagerUnregisterFontForData + 2852539
2   libcef.dylib                    0x01a69f8c mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 14123756
3   libcef.dylib                    0x01a69b73 mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 14122707
4   libcef.dylib                    0x01a69a79 mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 14122457
5   libcef.dylib                    0x01976f3b mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 13128347
6   libcef.dylib                    0x019777c6 mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 13130534
7   libcef.dylib                    0x01977678 mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 13130200
8   libcef.dylib                    0x019792ab mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 13137419
9   libcef.dylib                    0x01979239 mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 13137305
10  libcef.dylib                    0x00d05bbc mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 81692
11  libcef.dylib                    0x00d05e40 mac_plugin_interposing::NotifyBrowserOfPluginHideWindow(unsigned int, CGRect) + 82336
12  libsystem_pthread.dylib         0x92973ecf _pthread_body + 138
13  libsystem_pthread.dylib         0x92973e45 _pthread_start + 162
14  libsystem_pthread.dylib         0x92971f0e thread_start + 34

NOTE: this particular function was crashing on 10.6 (#4394) and that's when we discovered there was a library incompatibility between the 10.6 and 10.7 Mac SDKs. So I wouldn't be surprised if there is another incompatibility that exists between 10.7 and 10.10; this may be a fact of life on Yosemite until we upgrade CEF. We will need to verify that it is fixed with a newer build of CEF and file an issue with the CEF repo to fix if it isn't.

This particular code lives on the Chromium side so it's hopefully fixed with the newer SDK.

@peterflynn Can we reproduce this internally? I'm going to produce new CEF builds tomorrow so I'm wondering if anyone on Yosemite could verify that it is fixed. @matthewoates would you be available to test this with a newer build of Brackets if one becomes available next week?

[matthewoates]

Of course I'll check out the new build. I haven't been able to repro the issue without any extensions, but I can possibly narrow it down by uninstalling a few. I imagine that even if it's an extension that's causing the crash, you guys would still want that fixed.

[peterflynn]

@matthewoates Here are instructions for quickly turning extensions on & off: https://github.com/adobe/brackets/wiki/Troubleshooting#disabling-extensions-individually. If you could let us know which extension is causing this, that would be very helpful -- thanks!

[peterflynn]

@JeffryBooher Are you sure the stack is symbolized? I thought NotifyBrowserOfPluginHideWindow plus a huge offset (13-14MB in most of those frames) was the hallmark of an unsymbolized stack...