<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FIREBIRD: Crash in: libc-2.27.so when Save As of an ODB overtop of an existing ODB if the target has been opened in current session" href="https://bugs.documentfoundation.org/show_bug.cgi?id=120042#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FIREBIRD: Crash in: libc-2.27.so when Save As of an ODB overtop of an existing ODB if the target has been opened in current session" href="https://bugs.documentfoundation.org/show_bug.cgi?id=120042">bug 120042</a> from <a class="email" href="mailto:drewjensen.inbox@gmail.com" title="Drew Jensen <drewjensen.inbox@gmail.com>"> Drew Jensen</a> <pre>(In reply to Terrence Enger from <a href="show_bug.cgi?id=120042#c2">comment #2</a>) > These observations from debian-buster: daily Linux dbgutil bibisect > repository version 2018-09-22, and a local build of commit f74b8882 > (2018-09-20) plus the (presumably irrelevant) patch set 7 from > <<a href="https://gerrit.libreoffice.org/#/c/60048/">https://gerrit.libreoffice.org/#/c/60048/</a>>. > > I see the crash only if I browse table data in the first-opened file. > Additionally in this case, the title of the database window still > shows the name of the second-opened database file after I have saved > it over the first-opened one. > > I am setting status NEW. yes - I should of come back and clarified that. The issue only triggers if a connection to the database has been established in the first document. In fact I believe there are couple of other issues open right now that look to have a root cause tied to the connection not being freed up as the document is closed. I could go find those and cross reference them or maybe this is worth a meta issue dealing with connection life cycle management?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>