[Libreoffice-bugs] [Bug 132775] Crash with signature typelib_typedescriptionreference_release on FILEOPEN

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Jun 17 12:32:24 UTC 2020


https://bugs.documentfoundation.org/show_bug.cgi?id=132775

cybermonktitan at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|1                           |0
             Status|NEEDINFO                    |UNCONFIRMED

--- Comment #3 from cybermonktitan at gmail.com ---
I would love to be able to provide a sample document, because that means I can
reproduce the issue. I've tried, with the same documents as well as with
others, and I still work the way I described on a near-daily basis. I have not
seen this beyond the two instances in the original report.

The stack trace indicates this was caused by a mutex release. The first
thoughts then (to me, as a software engineer) are a double release or an
unacquired release. The latter is probably not the case (those tend to be
noticeable) so it seems most likely that we're looking at a rare race condition
that can lead to a double release. I am very much aware of how hard finding
those can be.

I see two possible ways forward. One is detecting the double release and
somehow dealing with it or getting information from that. That would be a
workaround for the crash and still indicates another problem since apparently
some mutex-protected code just ran without that protection - and you still
won't know where the initial release came from without very expensive
self-debugging mutexes with explicit active-lock lists. The other is going
through all uses of this mutex and making sure they are correctly acquired and
released in all possible circumstances, which can be incredibly tedious
depending on how widespread this mutex is.

Beyond these thoughts I can be of no help, I'm afraid.

I will change the status back to UNCONFIRMED despite not providing a document.
It's up to the team where to take it from there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200617/d32c3515/attachment-0001.htm>


More information about the Libreoffice-bugs mailing list