UNCONFIRMED Bug 63923
WebKit::PluginView::m_pendingURLRequestsTimer should use RunLoop::current() 
https://bugs.webkit.org/show_bug.cgi?id=63923
Summary WebKit::PluginView::m_pendingURLRequestsTimer should use RunLoop::current()
jaebok.lee
Reported 2011-07-05 01:07:18 PDT
I am using WebKit2 with ProcessModel::ProcessModelSharedSecondaryThread. When I use Plugin, a crash was invoked. I found that WebKit::PluginView::m_pendingURLRequestsTimer use RunLoop::main(). I think RunLoop::current() is right because WebKit::PluginView should work in WebProcess context. Please check this point.
Attachments
Add attachment proposed patch, testcase, etc.
Sam Weinig
Comment 1 2011-07-05 11:09:51 PDT
ProcessModelSharedSecondaryThread is currently not expected to work, there are numerous issues like this one lurking around.
Anders Carlsson
Comment 2 2011-07-05 11:11:42 PDT
(In reply to comment #0) > I am using WebKit2 with ProcessModel::ProcessModelSharedSecondaryThread. > > When I use Plugin, a crash was invoked. > > I found that WebKit::PluginView::m_pendingURLRequestsTimer use RunLoop::main(). > > I think RunLoop::current() is right because WebKit::PluginView should work in WebProcess context. > > > Please check this point. I think it should be I think WebProcess::shared().runLoop().
jaebok.lee
Comment 3 2011-07-08 01:18:01 PDT
When do you expect it works? (In reply to comment #1) > ProcessModelSharedSecondaryThread is currently not expected to work, there are numerous issues like this one lurking around.
Note You need to log in before you can comment on or make changes to this bug.