Closed GoogleCodeExporter closed 9 years ago
I just wanted to add that this appears to be happening when I manually call
CloseBrowser() on each of my browser instances *before* calling CefShutdown().
For the record, I'm using CEF 1 in multithreaded and offscreen rendering mode.
Some more observations on triggering this issue:
* If I use the middle-mouse button to open a new browser instance when clicking on a link, the issue does not occur when I later attempt to call CloseBrowser().
* If open a second browser instance manually with an empty URL and then browse somewhere, the issue then occurs when I later attempt to call CloseBrowser().
Original comment by dreijer...@gmail.com
on 16 Apr 2012 at 3:04
This appears to be an assertion and not a crash. Do you see the same problem
when running using the release executable?
Original comment by magreenb...@gmail.com
on 16 Apr 2012 at 4:08
Right, it's not a crash, but it happens on a thread that isn't my main thread
so I never get a chance to see the assertion and thus my application is
essentially hung forcing me to kill it (same end result essentially :).
I'm not sure how I'd see this problem if I link against a release build since
assertions are then turned off.
Original comment by dreijer...@gmail.com
on 16 Apr 2012 at 4:15
@comment#3: If there are no crashes or unexpected behavior in release build
then this assertion is unlikely to be a production issue.
Original comment by magreenb...@gmail.com
on 16 Apr 2012 at 4:35
Haha, I'll definitely check it, but it certainly depends on what the assertion
is about. If I'm triggering a code path in Chromium that absolutely shouldn't
be hit simply by closing a browser instance, how do I know this won't affect
other browser windows I'll be creating subsequently, which might or might not
bring down my entire application? :)
Original comment by dreijer...@gmail.com
on 16 Apr 2012 at 4:38
#comment#5: I looked at the code in question. My opinion is that, unless it's
crashing in release build, it's unlikely to be a production issue :-).
Original comment by magreenb...@gmail.com
on 16 Apr 2012 at 4:52
We should, of course, fix it if possible since it's annoying to developers and
likely indicates a bug somewhere, even if that bug isn't a production issue
per-say.
Original comment by magreenb...@gmail.com
on 16 Apr 2012 at 4:54
#comment#7: Yeah, was just about to say that. It might get a little annoying
for us developers in the long run. :)
Anywho, release builds seem to be okay. I'm seeing no WerFaults or anything
else and my application shuts down fine.
Original comment by dreijer...@gmail.com
on 16 Apr 2012 at 5:01
Original comment by magreenb...@gmail.com
on 22 May 2012 at 3:44
Should be filed as a bug with the Chromium/V8 project if it still occurs with
the newest CEF release build.
Original comment by magreenb...@gmail.com
on 3 Oct 2012 at 5:49
Original issue reported on code.google.com by
dreijer...@gmail.com
on 16 Apr 2012 at 2:42