Yeah, but it's crashing much later so the dump / stack trace wouldn't be that useful. I'm crashing in the OnLoadEnd() callback because of the presence of a "cef-error:" URL. I can see that the body of the page was replaced by an error message indicating that it had timed out. This is on Windows. We pulled it from
http://chromiumembedded.googlecode.com/svn/trunk/cef1 @ rev 1103 and
http://src.chromium.org/svn/trunk/src @ rev 176706 back in February of 2013.
I could fix it to not crash in the event of a cef-error URL, but I'd really like to know how it's even getting there. From my experimentation, if you don't call StopLoad() in the OnLoadError(), it seems to proceed to call OnLoadStart() and OnLoadEnd() for the error text. If you do call StopLoad(), it doesn't do that. I can't find any other way to end up in OnLoadEnd() with a cef-error URL.