Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
None
-
5.15.1
-
None
-
4e828b3bd2d410151dc2574d084bed631dac42ca (qt/qtwebengine-chromium/80-based)
Description
After upgrading to Qt 5.15.1, I've noticed frequent renderer process crashes, most often happening after logging on somewhere. The easiest way I've found to reproduce this is:
- Open https://groups.google.com/a/chromium.org/forum/#!msg/graphics-dev/ImZS-J1MKHI/MfWTUk--BwAJ in simplebrowser
- Log in with your Google Account
- If you don't get a crash yet, open the same URL again via the address bar
I've also gotten reports for crashes when logging into lloydsbank.com, https://myaccount.capitalone.co.uk/login and https://transferwise.com/login2/ but those are probably not as easy to reproduce.
Stack:
#0 0x00007fc3461bdb7b in blink::RTCPeerConnectionHandler::Observer::OnInterestingUsageImpl(int) () at /usr/lib/libQt5WebEngineCore.so.5 #1 0x00007fc3442caae4 in base::OnceCallback<void ()>::Run() && () at ../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/callback.h:98 #2 base::TaskAnnotator::RunTask(char const*, base::PendingTask*) () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/task/common/task_annotator.cc:142 #3 0x00007fc3442dd655 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, bool*) () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:365 #4 0x00007fc3442ddaa7 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:219 #5 0x00007fc3442930b6 in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/message_loop/message_pump_default.cc:39 #6 0x00007fc3442db6c8 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:463 #7 0x00007fc3442b6622 in base::RunLoop::Run() () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/base/run_loop.cc:156 #8 0x00007fc3466a97ff in content::RendererMain(content::MainFunctionParams const&) () at ./../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/content/renderer/renderer_main.cc:223 #9 0x00007fc343df107c in content::RunZygote(content::ContentMainDelegate*) () at ../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/content/app/content_main_runner_impl.cc:499 #10 0x00007fc343df17e8 in content::ContentMainRunnerImpl::Run(bool) () at ../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/content/app/content_main_runner_impl.cc:880 #11 0x00007fc3453deb4c in service_manager::Main(service_manager::MainParams const&) () at ../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/services/service_manager/embedder/main.cc:425 #12 0x00007fc343def886 in content::ContentMain(content::ContentMainParams const&) () at ../../../../qtwebengine-everywhere-src-5.15.1/src/3rdparty/chromium/content/app/content_main.cc:19 #13 0x00007fc34257d25b in QtWebEngineCore::processMain(int, char const**) (argc=<optimized out>, argv=<optimized out>) at ../../../../qtwebengine-everywhere-src-5.15.1/src/core/process_main.cpp:85 #14 0x000055702b26e0e4 in main(int, char const**) (argc=<optimized out>, argv=0x7ffe993c9fe8) at ../../../qtwebengine-everywhere-src-5.15.1/src/process/main.cpp:130
When running with --single-process, a different crash happens - not sure if those are related, so I'm going to open a separate issue for that.
Attachments
For Gerrit Dashboard: QTBUG-86752 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
315691,2 | [Backport] Fix for bug 1071327 | 80-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |