RESOLVED FIXED 120100
Assertion failure in WebCore::StorageTracker::deleteOrigin
https://bugs.webkit.org/show_bug.cgi?id=120100
Summary Assertion failure in WebCore::StorageTracker::deleteOrigin
Ryosuke Niwa
Reported 2013-08-20 20:21:13 PDT
Saw this on inspector/editor/text-editor-line-breaks.html Thread 17 Crashed:: WebCore: LocalStorage 0 com.apple.JavaScriptCore 0x000000010483e86a WTFCrash + 42 (Assertions.cpp:342) 1 com.apple.WebCore 0x00000001075364b2 WebCore::StorageTracker::deleteOrigin(WebCore::SecurityOrigin*) + 130 (StorageTracker.cpp:436) 2 com.apple.WebCore 0x00000001075357fd WebCore::StorageTracker::deleteOriginWithIdentifier(WTF::String const&) + 61 (StorageTracker.cpp:430) 3 com.apple.WebCore 0x0000000107522fb5 WebCore::StorageAreaSync::deleteEmptyDatabase() + 421 (StorageAreaSync.cpp:512) 4 com.apple.WebCore 0x0000000107525002 WTF::FunctionWrapper<void (WebCore::StorageAreaSync::*)()>::operator()(WebCore::StorageAreaSync*) + 114 (Functional.h:218) 5 com.apple.WebCore 0x0000000107524f85 WTF::BoundFunctionImpl<WTF::FunctionWrapper<void (WebCore::StorageAreaSync::*)()>, void (WebCore::StorageAreaSync*)>::operator()() + 53 (Functional.h:496) 6 com.apple.WebCore 0x0000000107402a52 WTF::Function<void ()>::operator()() const + 114 (Functional.h:704) 7 com.apple.WebCore 0x000000010752ed1b WebCore::StorageThread::threadEntryPoint() + 187 (StorageThread.cpp:80) 8 com.apple.WebCore 0x000000010752ebb5 WebCore::StorageThread::threadEntryPointCallback(void*) + 21 (StorageThread.cpp:72) 9 com.apple.JavaScriptCore 0x00000001048848b0 WTF::threadEntryPoint(void*) + 144 (Threading.cpp:70) 10 com.apple.JavaScriptCore 0x0000000104885258 WTF::wtfThreadEntryPoint(void*) + 104 (ThreadingPthreads.cpp:195) 11 libsystem_c.dylib 0x00007fff8edcc7a2 _pthread_start + 327 12 libsystem_c.dylib 0x00007fff8edb91e1 thread_start + 13 http://build.webkit.org/results/Apple%20MountainLion%20Debug%20WK1%20(Tests)/r154376%20(9569)/results.html
Attachments
Brian Burg
Comment 1 2014-12-17 17:51:57 PST
Tim fixed this earlier in the year.
Note You need to log in before you can comment on or make changes to this bug.