search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Crash in Brackets Sprint 30 #4721

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by dangoor Monday Sep 09, 2013 at 14:58 GMT Originally opened as https://github.com/adobe/brackets/issues/5132

We've had two crash reports for Sprint 30.@cfjedimaster reported a crash (with no associated slowdown) while working on a file with unsaved data.

The crash log turned up a problem that arose in v8's parser.

core-ai-bot commented 3 years ago

Comment by dangoor Monday Sep 09, 2013 at 15:02 GMT

Adding the "Mac only" label, because the two reports we had were both from Mac users.

core-ai-bot commented 3 years ago

Comment by njx Monday Sep 09, 2013 at 16:23 GMT

Unfortunately I completely failed to write down the procedure I figured out for symbolizing a crash log like this, but it basically involved downloading the symbol file for the appropriate version of CEF, cutting the column of stack addresses out of the stack trace, and using atos to do the lookup. I can look at this later in the afternoon, but am blocked by meetings for most of the day.

core-ai-bot commented 3 years ago

Comment by njx Monday Sep 09, 2013 at 16:23 GMT

Assigning to me for now.

core-ai-bot commented 3 years ago

Comment by dangoor Monday Sep 09, 2013 at 16:59 GMT

I did write down the procedure for symbolizing a crash log. I'm in meetings until noon pacific, but I could steal this from you and symbolize the stack trace after that.

core-ai-bot commented 3 years ago

Comment by njx Monday Sep 09, 2013 at 17:02 GMT

Looks like I'm free at 1 PT, so if you're free before that feel free to grab it, otherwise I can look at it then.

core-ai-bot commented 3 years ago

Comment by dangoor Monday Sep 09, 2013 at 19:09 GMT

This appears to be a v8 bug. I'm hoping that we can find out if it's been fixed already. I'm going to mark this tracking for now, because I don't think there's anything we can do on our end just yet.

core-ai-bot commented 3 years ago

Comment by Janpot Monday Sep 09, 2013 at 19:42 GMT

@dangoor Like you asked on thread https://groups.google.com/forum/?fromgroups#!topic/brackets-dev/PHvGHgmKEvc here's my crash log, I also want to add that I've seen the same slowdown before with Ctrl-X on windows as well

(edited by@dangoor to move the crashlog elsewhere.)

This crash log shows an error in v8's incremental GC.

core-ai-bot commented 3 years ago

Comment by dangoor Monday Sep 09, 2013 at 20:08 GMT

Thanks for the info@Janpot. Your crash appears to be in v8 also, but in a different place.

core-ai-bot commented 3 years ago

Comment by pthiess Friday Sep 13, 2013 at 17:13 GMT

Adding recommendations from Niklas to get additional information. At this point I lower the priority as we don't see a high volume and we don't have repro steps.

1) It would be useful if we can get a core dump for the crashing process.

On Mac OS X, add "limit core unlimited" to /etc/launchd.conf and reboot the machine. Future crashes will produce core dumps in /cores/core.

2) Additional useful information could come from V8 tracing. If it indeed is a bug in the V8 parser, it would be useful to know which piece of JS that triggered it. I am not familiar with how command line flags can be provided in CEF, but in Chromium --js-flags="--prof --log-timer-events" will enable fine-grained logging in v8 (ends up in v8.log).

core-ai-bot commented 3 years ago

Comment by cfjedimaster Saturday Sep 14, 2013 at 14:11 GMT

As just an FYI, I just had this happen again. This time while running Brackets from source, not a release build. I had literally just sat down to do some work, changed my project, turned on Live Connect, and typed some HTML when it went white. I'm going to do the limit action now and reboot.

Just noticed - I don't have /etc/launchd.conf.

core-ai-bot commented 3 years ago

Comment by njx Saturday Sep 14, 2013 at 20:11 GMT

@cfjedimaster - can you post your new crash log so we can verify it's the same crash? Thanks.

core-ai-bot commented 3 years ago

Comment by nqn Monday Sep 16, 2013 at 15:35 GMT

@cfjedimaster sorry to hear you experienced the crash once more.

From the stack traces, it appears to be memory/GC issues. It would be extremely useful to get a core file for the crash. If /etc/launchd.conf doesn't exist already, just go ahead and create it. It will work after a reboot. Core files will be placed in /cores/< pid >.core Note that core files can be fairly large (GB+), so you might want to disable it in the future.

We have reported the two incidents to the V8 developers and will follow up with any update on the issue.

core-ai-bot commented 3 years ago

Comment by cfjedimaster Monday Sep 16, 2013 at 21:57 GMT

I've added it and will reboot soon.

On Mon, Sep 16, 2013 at 10:36 AM, Niklas Quarfot Nielsen < notifications@github.com> wrote:

@cfjedimaster https://github.com/cfjedimaster sorry to hear you experienced the crash once more.

From the stack traces, it appears to be memory/GC issues. It would be extremely useful to get a core file for the crash. If /etc/launchd.conf doesn't exist already, just go ahead and create it. It will work after a reboot. Core files will be placed in /cores/.core Note that core files can be fairly large (GB+), so you might want to disable it in the future.

We have reported the two incidents to the V8 developers and will follow up with any update on the issue.

— Reply to this email directly or view it on GitHubhttps://github.com/adobe/brackets/issues/5132#issuecomment-24519293 .

Raymond Camden, Adobe Developer Evangelist

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

core-ai-bot commented 3 years ago

Comment by njx Monday Sep 16, 2013 at 22:15 GMT

Hey--would still like to get your latest crash log (even if you don't have a core dump for it) so we can make sure it's the same crash. Thanks.

core-ai-bot commented 3 years ago

Comment by cfjedimaster Monday Sep 16, 2013 at 22:20 GMT

Sorry - missed it:

https://dl.dropboxusercontent.com/u/88185/Brackets%20Helper_2013-09-14-090833_Raymonds-MacBook-Pro.crash

On Mon, Sep 16, 2013 at 5:16 PM, Narciso Jaramillo <notifications@github.com

wrote:

Hey--would still like to get your latest crash log (even if you don't have a core dump for it) so we can make sure it's the same crash. Thanks.

Raymond Camden, Adobe Developer Evangelist

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

core-ai-bot commented 3 years ago

Comment by njx Tuesday Sep 17, 2013 at 05:48 GMT

@cfjedimaster - thanks for the new stack. Were you using the current shell from Sprint 31, or the one from Sprint 30?

core-ai-bot commented 3 years ago

Comment by cfjedimaster Tuesday Sep 17, 2013 at 18:14 GMT

... I hate to say, I'm not 100% sure. I had switched to Sprint 31 a few days ago, but after a reboot had loaded up 30. I can't honestly say what it was at this time. Sorry!

On Tue, Sep 17, 2013 at 12:49 AM, Narciso Jaramillo < notifications@github.com> wrote:

@cfjedimaster https://github.com/cfjedimaster - thanks for the new stack. Were you using the current shell from Sprint 31, or the one from Sprint 30?

— Reply to this email directly or view it on GitHubhttps://github.com/adobe/brackets/issues/5132#issuecomment-24565473 .

Raymond Camden, Adobe Developer Evangelist

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

core-ai-bot commented 3 years ago

Comment by dangoor Tuesday Sep 24, 2013 at 14:00 GMT

I just encountered what I'm assuming is this crash for the first time. I haven't generated a stack trace for it yet, but here's the crash log

core-ai-bot commented 3 years ago

Comment by nqn Tuesday Sep 24, 2013 at 16:12 GMT

FYI One of our reported issues (http://code.google.com/p/chromium/issues/detail?id=291020) was merged into http://code.google.com/p/chromium/issues/detail?id=291034 and has now been reported as fixed.

core-ai-bot commented 3 years ago

Comment by njx Thursday Jan 30, 2014 at 00:19 GMT

@dangoor Wonder if we can close this now - I don't think we've been hearing about a lot of crashes lately and it seems likely this was fixed in CEF.

core-ai-bot commented 3 years ago

Comment by dangoor Thursday Jan 30, 2014 at 02:59 GMT

Yes, I say we close this. I haven't been seeing new crash reports.