Render Process Crash

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Render Process Crash

Postby cretz » Wed Sep 13, 2017 4:56 pm

In some cases, my renderer crashes with:

Code: Select all
[0913/164321.974:FATAL:ElementAnimations.cpp(112)] Check failed: *base_computed_style_ == *computed_style.


It happens only if my settings do have a cache path, and a bit after initialize, I open a new URL in my app, then ctrl+click a previously unvisited page (triggering OnOpenURLFromTab which I return true from) and open it in a new CEF browser. It crashes only the one I ctrl+clicked on (even though I do nothing in there and only open something in a new tab in my app).

I am having a hard time to reliably replicate this (in Windows). One way I just make sure to have a cache path, wait a couple secs after init, and go to http://doc.qt.io/qt-5/classes.html and start ctrl+clicking on class names I have never visited before until the error occurs and the crash occurs. I have turned on differing levels of verbosity but am not getting anywhere. It happens in all versions of CEF I try. Any ideas?
cretz
Techie
 
Posts: 34
Joined: Mon Jun 26, 2017 11:41 am

Re: Render Process Crash

Postby cretz » Wed Sep 13, 2017 5:04 pm

Ok this appears related to https://bugs.chromium.org/p/chromium/is ... ?id=571598 and https://bugs.chromium.org/p/chromium/is ... ?id=701250. I have a hard time easily determining which release https://chromium.googlesource.com/chrom ... 860a29fa2f has or will appear in.
cretz
Techie
 
Posts: 34
Joined: Mon Jun 26, 2017 11:41 am

Re: Render Process Crash

Postby magreenblatt » Wed Sep 13, 2017 5:09 pm

You can use the "Find Releases" widget at https://omahaproxy.appspot.com
magreenblatt
Site Admin
 
Posts: 12382
Joined: Fri May 29, 2009 6:57 pm

Re: Render Process Crash

Postby cretz » Thu Sep 14, 2017 10:48 am

Thanks. As I feared, it landed in 59 which is two versions ago, so I still experience this crash, but I cannot replicate the crash in Chrome. I will work on replicating it in CEF even though it is likely a Chromium issue that they don't trigger with how their browser is used. Any guesses on the code paths that cause the crash or any replication method is welcome.
cretz
Techie
 
Posts: 34
Joined: Mon Jun 26, 2017 11:41 am


Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 44 guests