Bug 111171 - [EFL] [IndexedDB] Cursor-advance-workers crashes sometimes
Summary: [EFL] [IndexedDB] Cursor-advance-workers crashes sometimes
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit EFL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 106732
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-01 05:52 PST by Riju
Modified: 2017-03-11 10:42 PST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Riju 2013-03-01 05:52:52 PST
GTK has a crash for the same test , but it does not look entirely similar : Bug 107377

crash log for WebProcess (pid <unknown>):
STDOUT: <empty>
STDERR: ERROR: Thread name "com.apple.WebKit.ProcessLauncher" is longer than 31 characters and will be truncated by Visual Studio
STDERR: /home/riju/WebKit/Source/WTF/wtf/Threading.cpp(78) : WTF::ThreadIdentifier WTF::createThread(WTF::ThreadFunction, void*, const char*)
STDERR: ERROR: Thread name "com.apple.WebKit.EventDispatcher" is longer than 31 characters and will be truncated by Visual Studio
STDERR: /home/riju/WebKit/Source/WTF/wtf/Threading.cpp(78) : WTF::ThreadIdentifier WTF::createThread(WTF::ThreadFunction, void*, const char*)
STDERR: ERROR: Thread name "com.apple.WebKit.PluginProcessConnectionManager" is longer than 31 characters and will be truncated by Visual Studio
STDERR: /home/riju/WebKit/Source/WTF/wtf/Threading.cpp(78) : WTF::ThreadIdentifier WTF::createThread(WTF::ThreadFunction, void*, const char*)
STDERR: ASSERTION FAILED: active != (m_state == Active)
STDERR: /home/riju/WebKit/Source/WebCore/Modules/indexeddb/IDBTransaction.cpp(204) : void WebCore::IDBTransaction::setActive(bool)
STDERR: 1   0x7f29aa9c2127 WebCore::IDBTransaction::setActive(bool)
STDERR: 2   0x7f29aa9be78b WebCore::IDBRequest::dispatchEvent(WTF::PassRefPtr<WebCore::Event>)
STDERR: 3   0x7f29ab8ffacc WebCore::WorkerEventQueue::EventDispatcherTask::dispatchEvent(WebCore::ScriptExecutionContext*, WTF::PassRefPtr<WebCore::Event>)
STDERR: 4   0x7f29ab8ffb52 WebCore::WorkerEventQueue::EventDispatcherTask::performTask(WebCore::ScriptExecutionContext*)
STDERR: 5   0x7f29ab907205 WebCore::WorkerRunLoop::Task::performTask(WebCore::WorkerRunLoop const&, WebCore::ScriptExecutionContext*)
STDERR: 6   0x7f29ab906d41 WebCore::WorkerRunLoop::runInMode(WebCore::WorkerContext*, WebCore::ModePredicate const&, WebCore::WorkerRunLoop::WaitMode)
STDERR: 7   0x7f29ab906abb WebCore::WorkerRunLoop::run(WebCore::WorkerContext*)
STDERR: 8   0x7f29ab90ae7d WebCore::WorkerThread::runEventLoop()
STDERR: 9   0x7f29ab8f48af WebCore::DedicatedWorkerThread::runEventLoop()
STDERR: 10  0x7f29ab90ad98 WebCore::WorkerThread::workerThread()
STDERR: 11  0x7f29ab90aaec WebCore::WorkerThread::workerThreadStart(void*)
STDERR: 12  0x7f29ac07bf2d
STDERR: 13  0x7f29ac0a3c12
STDERR: 14  0x7f29a3c52e9a
STDERR: 15  0x7f29aed8fcbd clone
Comment 1 Joshua Bell 2013-03-07 13:19:01 PST
That ASSERT is indicating that something has either:

(1) Not correctly deactivated a new transaction on return from script
(2) Not correctly activated/deactivated a transaction during an event handler

It's probably similar to the issue noted here:

https://bugs.webkit.org/show_bug.cgi?id=101618

In the Chromium/V8 port we have code in the binding layer to implement (1) via the IDBPendingTransactionMonitor. Without looking at the code, my guess is that the GTK port is missing this step in some cases.
Comment 2 Joshua Bell 2013-03-07 13:19:14 PST
Er, EFL port, sorry.
Comment 3 Joshua Bell 2013-03-07 13:21:35 PST
Ah, this looks like a dupe of:

https://bugs.webkit.org/show_bug.cgi?id=106732
Comment 4 Michael Catanzaro 2017-03-11 10:42:30 PST
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.