Thanks glyph - really appreciate all the times you've answered my questions! QtWebEngineView is running a subprocess. /home/ubuntu/Qt5.8.0/5.8/gcc_64/libexec/QtWebEngineProcess --type=renderer --disable-accelerated-video-decode --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --use-gl=desktop --disable-webrtc-hw-encoding --primordial-pipe-token=032B94B57A61DAE34BD0F90551F9ABB6 --lang=en-US --enable-pinch --num-raster-threads=2 --content-image-texture-target=3553 QT can sometimes be helpful, but bug resolution can take a while. Any suggestions outside of twisted for detecting segfaults? I'm thinking just to monitor /var/log/syslog On Sat, Feb 25, 2017 at 11:59 PM, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
On Feb 25, 2017, at 4:41 PM, Kevin Mcintyre <kebin70@gmail.com> wrote:
I have a long running twisted pyqt process which occasionally throws a Received signal 11.
I believe it's in the underlying QtWebEngineView since the twisted process continues to run. Whatever the reason I would like to figure out a way to catch this and stop the reactor either in process, or by another process monitor. Any suggestions either twisted or otherwise would be greatly appreciated.
Presumably the QtWebEngineView is running a subprocess, then? This is really a Qt question rather than a Twisted question, because the QtWebEngineView should be emitting some kind of signal when its rendering process crashes. (If it doesn't I imagine you're just out of luck here and you should report a bug to the Qt developers...)
-glyph _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python