Bug Hunting Session
Bug 117842 - Firebird: Enabling connection pooling for firebird:sdbc driver crashes Libo when creating connection to data engine
Summary: Firebird: Enabling connection pooling for firebird:sdbc driver crashes Libo w...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Database-Firebird-Default
  Show dependency treegraph
 
Reported: 2018-05-28 04:45 UTC by Drew Jensen
Modified: 2019-06-01 02:49 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
crash dmp file from Libo 5.4.7.2 (467.26 KB, application/vnd.tcpdump.pcap)
2018-05-28 04:46 UTC, Drew Jensen
Details
Crash dmp file from Libo 6.1Beta1 (396.48 KB, application/vnd.tcpdump.pcap)
2018-05-28 04:47 UTC, Drew Jensen
Details
bt with debug symbols (13.29 KB, text/plain)
2018-05-28 20:44 UTC, Julien Nabet
Details
bt from pthread_mutex_lock failed (14.30 KB, text/plain)
2018-05-28 21:06 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Drew Jensen 2018-05-28 04:45:10 UTC
Description:
Checked this with 5.4.7.2, 6.0.4, 6.1Beta1, 6.2Alpha0
Crash in all of them
Also checked connection pooling enabled for sdbc.hsql in all of the above, no crash, no problems.

Steps to Reproduce:
1. Open the Options dialog Tools->Options
2. navigate to the Libreoffice Base->Connections section
3. Place a tick mark in 'Enable connection pooling'
4. In the list of drivers select the com.sun.star.comp.sdbc.firebird.Driver
5. Place a tick mark in 'Enable pooling for this Driver' 
6. Accept the default timeout value
7. Click OK to close the options dialog
8. Click Create: New Database
9. Select Firebird Embedded for database type.
10. Click finished, save the new file with some name
10a Alternatively open an ODB file which uses the sdbc.firebird driver or for 6.1 and 6.1 open an ODB file using HSQLdb embedded and allow the migration assistant to start.

Actual Results:  
Crash


Expected Results:
Base file loads and connection to database engine is established.


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/66.0.3359.181 Chrome/66.0.3359.181 Safari/537.36
Comment 1 Drew Jensen 2018-05-28 04:46:13 UTC
Created attachment 142322 [details]
crash dmp file from Libo 5.4.7.2
Comment 2 Drew Jensen 2018-05-28 04:47:20 UTC
Created attachment 142323 [details]
Crash dmp file from Libo 6.1Beta1
Comment 3 Julien Nabet 2018-05-28 20:44:28 UTC
Created attachment 142359 [details]
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I could reproduce this.
Comment 4 Julien Nabet 2018-05-28 20:59:22 UTC
BTW, I noticed this on console:
warn:legacy.osl:3659:3659:svtools/source/uno/genericunodialog.cxx:288: OGenericUnoDialog::OnDialogDying: where does this come from?
warn:sal.osl.mutex:3659:3659:sal/osl/unx/mutex.cxx:100: pthread_mutex_lock failed: Invalid argument
Comment 5 Julien Nabet 2018-05-28 21:06:06 UTC
Created attachment 142360 [details]
bt from pthread_mutex_lock failed
Comment 6 QA Administrators 2019-06-01 02:49:18 UTC
Dear Drew Jensen,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug