[Webkit-unassigned] [Bug 190178] New: Add release assertion to ensure m_owningPointerForClose is null in UniqueIDBDatabase::invokeOperationAndTransactionTimer()

[bugzilla-daemon at webkit.org]

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

            Bug ID: 190178
           Summary: Add release assertion to ensure
                    m_owningPointerForClose is null in
                    UniqueIDBDatabase::invokeOperationAndTransactionTimer(
                    )
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sihui_liu at apple.com

As in rdar://problem/44902833, RELEASE_ASSERT(!m_owningPointerForClose) in UniqueIDBDatabase::scheduleShutdownForClose() frequently gets hit, which means m_owningPointerForClose is already acquired for close and we should not reach scheduleShutdownForClose. 
Since scheduleShutdownForClose() is fired on timer, it's hard to tell which function dispatches it a second time from the crash log.

The added release assertions in the invoke function should help reveal the probblematic code path.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20181002/4e11fbe6/attachment-0001.html>