Closed GoogleCodeExporter closed 8 years ago
There is a topic on CEF forum regarding this matter:
http://magpcss.org/ceforum/viewtopic.php?f=6&t=10252
I'm not sure how threads in Qt work.
Original comment by czarek.t...@gmail.com
on 27 Nov 2012 at 2:56
[deleted comment]
Original comment by czarek.t...@gmail.com
on 27 Nov 2012 at 3:06
Fixed in revision 2469d5441fd3.
The solution was to assign None to QApplication before calling shutdown:
app = None
cefpython.Shutdown()
This fix removed errors in the console, I'm assuming it also fixed the crash,
but as I couldn't reproduce it, I'm not 100% sure, so better test it.
Original comment by czarek.t...@gmail.com
on 27 Nov 2012 at 9:46
Verified. Issue disappears if None is assigned to app. App must be garbage
collected by null assignment but not sure how/why it was causing the error in
first place.
Original comment by codeprop...@gmail.com
on 27 Nov 2012 at 11:34
I guess Qt could still run some internal threads that collided with shutdown or
something. It makes sense, we called cefpython.Initialize() before QApplication
was initialized, so we should destroy QApplication (it also needs to do some
cleanup, probably called in destructor) before cefpython.shutdown().
Original comment by czarek.t...@gmail.com
on 28 Nov 2012 at 12:39
Project will move to Github. Find this issue at the new address (soon):
https://github.com/cztomczak/cefpython/issues/30
Original comment by czarek.t...@gmail.com
on 24 Aug 2015 at 6:26
Original issue reported on code.google.com by
codeprop...@gmail.com
on 27 Nov 2012 at 2:47