Chrome "Aw, snap!" crashes possibly related to WebRTC

[Jonathan Stewart]

I'm supporting a WebRTC based call center application for a client and they are seeing irregular but recurring crashes during calls. Checking some of the crash dumps and doing system stat tracking I was able to pin some of them down to a memory leak but the latest batch appear to be something else. Looking at the minidump files the exception code is 0x80000003 which is labeled as "A breakpoint was encountered" but these are release builds not running in a debugger. What else can I do/provide to help figure out the cause of the crashes? Unfortunately I can't reproduce the crash on demand and I can't install anything that needs a license (e.g. Visual Studio) on the systems where it is crashing. It seems to be an average of a crash every 4 days per system and they have 4 systems.

Thanks,

Jonathan

[PhistucK]

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

[Primiano Tucci]

Please file a bug and specify the Server ID that you (or your customers) see in chrome://crashes

The crash server will have the full crash stack and help triaging the bug.

> Looking at the minidump files the exception code is 0x80000003 which is labeled as "A breakpoint was encountered" but these are release builds not running in a debugger

This can be due to hitting CHECK (asserts) in the codebase

[Jonathan Stewart]

You can reply with a link to the found or created issue and might get triaged (and fixed) faster. 

 

I couldn't find anything that matched so I filed this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=693068

For some reason these crashes aren't showing up in chrome://crashes but if I go to chrome://crash that shows up. Hopefully the stack trace I was able to grab and added to the bug report will help.