-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Debug build Hangs during Startup #5277
Comments
Low priority to @ingorichter |
I needed the Mac debugger last week and ran into this. It doesn't seem like "low priority" when you need it. :) Using git bisect, I isolated this problem to commit adobe/brackets-shell@fdea13a from pull request adobe/brackets-shell#281 by @RaymondLim. The code seems to go into an infinite loop. The menu works, but nothing happens when you select anything. Re-assigned to @RaymondLim . |
I cannot run a debug build on Windows either. Seems similar -- caught in an infinite loop. Looks like maybe a resource deadlock? Here's the callstack:
|
Bumping this up to Medium Priority. |
@redmunds I'm seeing the same thing on Mac (editor window becomes blank like WSOD) even after I revert my changes in adobe/brackets-shell#281. Below is the call stack on Mac and I think it's more useful than the one @redmunds got on Windows with explicit debugger break. It's a segmentation fault and maybe we should reach out to CEF team. ASSERTION FAILED: foundContainer |
Pull request adobe/brackets-shell#355 only fixes the specific issue on mac and still does not fix the other pre-existing issue that causes Brackets window going blank. |
@redmunds If you review the calll stack I pasted above, you will see that the crash (segmentation fault) is happening when rendering the editor. So I began suspecting that the crash was introduced in Brackets repo and not in Brackets-shell repo. And It took me several tries on brackets repo using "git bisect" and finally I found out that it is caused by @njx's commit 119b4ef for inline editor animation. I did verify that the debug crash happens with that commit (on both Windows and Mac platforms), but no crash if I checkout the prior one 73ca611. So reassigning to @njx to investigate it. Maybe it is a valid bug in CEF that we just uncover with this specific commit, but it will be nice if we can make some changes in our code to avoid this debug issue. |
Interesting... @njx I wonder if it's the |
@peterflynn Oops... spoke too soon. I just got a crash after switching project, but definitely not that easy to crash w/o these CSS properties. Below is the call stack I got with this change. ASSERTION FAILED: m_verifier.isSafeToUse() |
That second crash looks like a v8 crash, so it might not be related to the renderer. |
Yay! I can run Debug builds on both Mac and Windows again! |
But you still can't change project with the dropdown. Otherwise, you will hit the second crash. |
I didn't test exhaustively, but I was able to switch to another project and then switch back to the first project. |
Ok, the second crash doesn't happen on every click. But occasionally it can happen when hovering, clicking and double-clicking on file/folder in the file tree or X button before file in working set or the project dropdown list. |
Not sure I'm the right person to look at this since I don't have much experience debugging in the shell. @JeffryBooher or @bchintx maybe? |
I've not have any problems on OSX debugging although it is slower. The work-around that I suggest is to use the release binaries of CEF for building the debug version of the shell. That should get you past all of the assertions that seem to come up in the debug builds but crashers in the renderer may still occur in the release build of CEF. If it is a reproducible case then it's best to get that datapoint to Stefan-Teodor Craciun [email protected] and see if he can figure it out. Kind of hard to follow this thread but it sounds like this particular instance of the crash is in V8, so it will require someone with security access to V8 source in order to debug it or at least enough knowledge to know how to get it reported correctly to the V8 team. I'd start with running with the release binaries. If you can get past your crash with the release binaries then I don't think there is anything else we need to do about it. |
+1 to @JeffryBooher 's comment. I'm not seeing a crash debugging the shell on Windows now either, and commenting out the In addition to his workaround, on Windows, I'd also suggest just sandwiching any code that you want to debug with the following optimization-disabling switches:
Now, you can continue to build Release, be able to step thru the code quickly, but have non-mangled, full debug symbols for that section of code. |
@bchintx @JeffryBooher @redmunds Did anybody see this recently? Should we close it for now? |
@ingorichter I haven't needed a Debug build in while, but I can try again. |
@ingorichter the Windows Debug build still crashes on Startup even with CEF 1750. It's something in our JS that's causing it. It's the render process that dies. |
I think it is the node connection that is causing this crash in debug builds. Commenting |
Original Title: Brackets debug build on OSX crashes during startup
Result: the app crashes.
Same result on Windows.
The text was updated successfully, but these errors were encountered: