<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#c5">Comment # 5</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:lo_bugs@iseries-guru.com" title="Terrence Enger <lo_bugs@iseries-guru.com>"> Terrence Enger</a> <pre>(In reply to Drew Jensen from <a href="show_bug.cgi?id=120042#c4">comment #4</a>) > (In reply to Terrence Enger from <a href="show_bug.cgi?id=120042#c2">comment #2</a>) > > ... only if I browse table data ... > > 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 I think that clicking <Tables> in the left pane to display the list of tables establishes the connection. Right? But I think I remember that that alone is not sufficient to trigger the later crash. > 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. When I re-open the first file and browse table data a second time, lsof shows the same number of occurrences of fd's and they have the same value. So maybe maintenance of the connection is a deliberate optimization. I doubt that the optimization is needed, and it is clearly not being done right. This report immediately reminded me of <a class="bz_bug_link bz_status_NEW " title="NEW - leaks a fd on closed odb: locks file on Windows share" href="show_bug.cgi?id=77141">bug 77141</a> "leaks a fd on closed odb: locks file on Windows share", but that is from 2014 and so is older than 6.0.6, which is said not to have the present problem. (The summary of <a class="bz_bug_link bz_status_NEW " title="NEW - leaks a fd on closed odb: locks file on Windows share" href="show_bug.cgi?id=77141">bug 77141</a> is not quite right: the leak happens on Linux too, but Linux is more tolerant of operations on still-open files.) After Save-As but while the database window is still open, lsof showed me the first-opened file 8 times (all with the same value for the fd). > I could go find those and cross reference them or maybe this is worth a meta > issue dealing with connection life cycle management? Or, perhaps a bug for life cycle management in general. Do we have that already?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>