otter v 0.9.11 some HTML5 pages crashing 2017-06-29, 07:35:47 I have build otter 0.9.11 for iMX6 soloX linuxBelow are some random errors observed for some HTML5 pages and page crashed. Error observed approximately after 1 hour (not instantly when switching pages). one more observation, QtWebengineProcess exited (/usr/lib/qt5/libexec/QtWebEngineProces).Some pages are working fine without any problem. Also tested same code for ubuntu 14.04 and works fine. I am using Qt 5.7.1 and otter build with QtWebengineIs this same problem mentioned here (https://bbs.archlinux.org/viewtopic.php?id=214026)?Errors on console -1) *** stack smashing detected ***: /usr/lib/qt5/libexec/QtWebEngineProcess --type=renderer --disable-accelerated-video-decode --enable-overlay-scrollbar --enable-pinch --enable-threaded-compositing --enable-viewport --main-frame-resizes-are-orientation-changes --profiler-timing=0 --use-gl=egl --disable-composited-antialiasing --lang=C --enable-pinch --num-raster-threads=1 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553 --channel=2306.2.1621294241 terminatedReceived signal 6[end of stack trace]2) Received signal 11 SEGV_MAPERR 0000a66dd9a0[end of stack trace]3) Received signal SEGV_ACCERR[end of stack trace]
Re: otter v 0.9.11 some HTML5 pages crashing Reply #1 – 2017-06-29, 08:05:12 @mad_king, try reproducing that using:https://github.com/OtterBrowser/test-qtwebengineIt looks like some sort of QtWebEngine issue.Also you should update to at least beta 12 (0.9.12) and consider testing using Qt SDK 5.9 (official Qt binaries).
Re: otter v 0.9.11 some HTML5 pages crashing Reply #2 – 2017-06-29, 11:11:15 Thanks for valuable inputs.Using test code i could able to reproduce the said issue. It seems something goes wrong with QtWebengine. As per this link (https://bbs.archlinux.org/viewtopic.php?pid=1639729#p1639729) this is related to GCC 6. First i'll check with this workaround.Thanks
Re: otter v 0.9.11 some HTML5 pages crashing Reply #3 – 2017-07-06, 22:21:30 *http://www.asahi.com/articles/ASK7551MXK75UTFK00B.html*Otter 0.9.91 weekly 183 QtWebEngine 64-bit version only *problem: japanese page broken.
Re: otter v 0.9.11 some HTML5 pages crashing Reply #4 – 2017-07-07, 07:40:20 @kanakomoerer, what exactly is broken there?Some images showing broken and correct rendering could be a good idea, I could use them to ask upstream developers.
Re: otter v 0.9.11 some HTML5 pages crashing Reply #5 – 2017-09-24, 06:30:11 Quote from: mad_king on 2017-06-29, 07:35:47I have build otter 0.9.11 for iMX6 soloX linuxBelow are some random errors observed for some HTML5 pages and page crashed. Error observed approximately after 1 hour (not instantly when switching pages). one more observation, QtWebengineProcess exited (/usr/lib/qt5/libexec/QtWebEngineProces).Some pages are working fine without any problem. Also tested same code for ubuntu 14.04 and works fine. I am using Qt 5.7.1 and otter build with QtWebengineIs this same problem mentioned here (https://bbs.archlinux.org/viewtopic.php?id=214026)?Errors on console -1) *** stack smashing detected ***: /usr/lib/qt5/libexec/QtWebEngineProcess --type=renderer --disable-accelerated-video-decode --enable-overlay-scrollbar --enable-pinch --enable-threaded-compositing --enable-viewport --main-frame-resizes-are-orientation-changes --profiler-timing=0 --use-gl=egl --disable-composited-antialiasing --lang=C --enable-pinch --num-raster-threads=1 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553 --channel=2306.2.1621294241 terminatedReceived signal 6[end of stack trace]2) Received signal 11 SEGV_MAPERR 0000a66dd9a0[end of stack trace]3) Received signal SEGV_ACCERR[end of stack trace]After detail investigation, this is not a qtwebengine (eventually not Otter) problem. This is related to RAM (with hardware and build system). Now it works as expected.@Emdek - Please mark it as solved.Thanks
Re: otter v 0.9.11 some HTML5 pages crashing Reply #6 – 2017-09-24, 10:02:54 @mad_king, I see.Well, we not use such prefixes here (like [solved]), that's more suitable for tickets system. ;-)