Summary: | REGRESSION(r211486): [GTK] Loading pages is broken | ||
---|---|---|---|
Product: | WebKit | Reporter: | Tomas Popela <tpopela> |
Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | bugs-noreply, cgarcia, inspector-bugzilla-changes, joepeck, mcatanzaro |
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=167683 |
Description
Tomas Popela
2017-02-02 08:54:22 PST
Errr wow. I guess step 1 is to rollout. My best guess is that the main run loop initialization added to InitializeThreading doesn't happen on the main thread?! An alternative solution would be to guard the main run loop initialization in Source/JavaScriptCore/runtime/InitializeThreading.cpp with PLATFORM(COCOA) guards. That feels a bit arbitrary, but since I can't test GTK to understand what is happening, and since GTK doesn't currently use the JSContext inspector code, it should be just fine. If I don't hear back by the end of the day I'll speculatively land this change. To start investigation a backtrace of all threads to see what is happening when RunLoop::initializeMainRunLoop is getting called on GTK would be important. I'd rather fix it properly than add a strange PLATFORM(COCOA) guard adding even more platform-dependent behavior. I didn't roll it out because our bots are not hitting this for some inexplicably reason, and since I know you can't test it. We'll figure something out. :) (In reply to comment #3) > I'd rather fix it properly than add a strange PLATFORM(COCOA) guard adding > even more platform-dependent behavior. > > I didn't roll it out because our bots are not hitting this for some > inexplicably reason, and since I know you can't test it. We'll figure > something out. :) Thanks! My best guess is MiniBrowser does something that WebKitTestRunners don't and triggers JavaScriptCore's thread initialization on a background thread. I missed this bug, but not #167776, where I submitted a patch, so marking this a dupl because the other one has a patch already. Please, guys, for GTK+ bugs remember to either use the WebKitGtk component or add webkitgtk to the CC *** This bug has been marked as a duplicate of bug 167776 *** |