Dartium crashes when setting breakpoints during setup

[sethladd]

We have three individuals here that got their Editor/Dartium into a broken state. No app would load into Dartium (Sunflower or custom). Dartium would Aw Snap immediately without ever displaying a URL.

I've attached the metadata directory from a user's machine. We can delete this .metadata, which seems to fix the problem.

Hopefully, this corrupted .metadata dir is enough to track down the problem. With the individuals experiencing this, it's not isolated.

Everyone had the latest integration build as of 2012-07-14

---

Attachment:
JWB_WS.zip (1.63 MB)

[devoncarew]

So, my workaround when Dartium aw snaps is to delete all breakpoints (via the remove all breakpoints button in the debugger view or from the Run menu). Generally, Dartium will fire up just fine on the next attempt. This doesn't get us any closer to a fix, but is at least a user workaround.

Does this work if you try it? The editor stores a lot of metadata in that .metadata directory, including the locations + info about current breakpoints. So by deleting the metadata, you may just be effectively doing the remove all breakpoints command -

[stevemessick]

mac64bit is causing many aw snaps while debugging.
////////////////////////////////////////////////////////////////////////////////////
Editor: 9474
OS: Mac OS X - i386 (10.7.4)
JVM: 1.6.0_33

SDK installed: true
Dartium installed: true

[sethladd]

Confirmed... the three troublesome installs were all 64 bit. Reports of a more stable 32 bit experience were heard from those users.

This was a pretty big deal, those three users were dead in the water until we figured out we could delete the metadata dir.

[DartBot]

This comment was originally written by branflak...@gmail.com

---

I had the aw snap crash on both 64 and 32bit.

I had it occur when.

1. by stopping debugging while on break and while quitting chromium while it is breaked(paused
2. By stopping the debugger (red) stop
3. By instantly debugging with
4. I got it more often if I stopped immediately during debugging and rerunning it quickly after
5. I got it after trying to run a file with no entry/main method then trying to run a file with main method

I had a better experience with 32 bit, but I still had the aw snaps.

Not sure that helps any b/c I couldn't find a pattern to what caused it, but those are some of the events that it had occurred in.

[DartBot]

This comment was originally written by branflak...@gmail.com

---

I found it happen most often after Command quitting chromium during a pause, stopping elipse debug, adding a break point and running debug again. Maybe it happened while walking and stopping...

[danrubel]

Set owner to @devoncarew.
Added this to the M1 milestone.

[devoncarew]

Renamed from "Corrupted .metadata causes Aw Snap dartium launches"

So, unfortunately I can't get this situation to reproduce consistently. When Dartium does get into this state however, every time I try and launch it, it crashes. The only recourse is to clear all breakpoints from the editor. The next time we launch Dartium, it'll start up just fine.

I'm not quite sure what causes this behavior to start, but I see it every few weeks or so.

---

Set owner to podivilov@google.com.
Removed Area-Editor label.
Added Area-Dartium label.
Changed the title to: "Dartium crashes when setting breakpoints during setup".

[DartBot]

This comment was originally written by podivilov@google.com

---

Added Started label.

[devoncarew]

On advice from Pavel, I have a CL to better manage when we set our breakpoints. We set them all, and wait for Dartium's responses, before we switch to the app's url and start the VM running.

CL: https://chromiumcodereview.appspot.com/10913278/

I have not been able to reproduce the crash, either before or after this CL. This was a very intermittent and hard to reproduce crash. We'll keep an eye out for future issues and re-open if necessary.

---

Set owner to @devoncarew.
Removed Area-Dartium label.
Added Area-Editor, Fixed labels.