Bug 93396 - LibreOffice 5.0 Crashes on Windows 8 64-bit when making JDBC connection (Windows 64bit)
Summary: LibreOffice 5.0 Crashes on Windows 8 64-bit when making JDBC connection (Wind...
Status: RESOLVED DUPLICATE of bug 93348
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: x86-64 (AMD64) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2015-08-12 20:08 UTC by Steven Shelton
Modified: 2015-11-19 13:55 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
backtrace using winDbg from crash caused by LibreOffice Base while opening a JDBC connection (25.19 KB, text/plain)
2015-10-30 10:59 UTC, Stefan M
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Shelton 2015-08-12 20:08:46 UTC
LibreOffice 5.0.0.5 64-bit version on Windows 8.1 box, 64 bit crashes when using JRE 1.8.0_5 64-bit to connect to an HSQLDB database with the JDBC. It seems to open Calc and Writer files just fine, and even initially opens Base documents, but as soon as you try to connect to the database (regardless of which application you are using: writer, calc, etc.) it crashes out.

Seems to work fine on 32-bit Windows boxes.
Comment 1 Steven Shelton 2015-08-12 20:59:05 UTC
FYI: uninstalled the 64-bit version of LO and installed the 32-bit version and it works flawlessly, so this is clearly an issue with the 64-bit version only.
Comment 2 Alex Thurgood 2015-08-13 10:19:12 UTC
We need someone else running Windows 64bit with LO 64bit to confirm.
Comment 3 Julien Nabet 2015-08-13 10:27:50 UTC
A bt could be very useful to locate the root cause in the code.
Comment 4 Steven Shelton 2015-08-14 13:23:10 UTC
Is there any way I can produce a backtrace? (Not a programmer; just an end-user, but if I can help squash this bug, I'll do what I can do help.)
Comment 6 Buovjaga 2015-09-08 09:28:09 UTC
Any luck with bt? https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Or any difference with LibO 5.0.1?
Comment 7 Stefan M 2015-10-30 10:59:45 UTC
Created attachment 120100 [details]
backtrace using winDbg from crash caused by LibreOffice Base while  opening a JDBC connection
Comment 8 Stefan M 2015-10-30 11:04:03 UTC
I have encountered the same problem. I could produce a backtrace and I hope it is complete because winDbg could not connect to the symbol server (see ERROR messages in the attached backtrace) 

The version(s) I have produced the backtrace with was 

LibreOffice 5.0.2.2 
JRE 1.8.64
Windows 7 Prof.
Comment 9 Alex Thurgood 2015-11-18 07:15:49 UTC
Steven : just to be absolutely clear, when you mention using JDBC and hsqldb, do you mean an external hsqldb instance, and not the internal, embedded default ?

I tested opening an embedded hsqldb ODB file on Windows 10, with LO 5032 64bit and 64bit JDK 1.8.0_66 and I experienced no crash.

Could you retest with the latest versions of LO and JDK (which has just been updated to u66 by Oracle) and report back here ?
Comment 10 Stefan M 2015-11-18 13:46:38 UTC
One thing I forgot in my backtrace comment was:

I am using the postgres jdbc driver and connect to a postgresql database on a different host. This worked flawlessly using OpenOffice and LibreOffice from Version 3.x onwards in a lot of different combinations with various versions of the postgresql jdbc driver.

Libreoffice 5.0.3 still crashes the moment I connect to the database. 

Under MacOS and Linux the same database connection works. 

Stefan
Comment 11 Alex Thurgood 2015-11-18 17:38:05 UTC
DUP of bug 93348 see comment 6 of that bug

*** This bug has been marked as a duplicate of bug 93348 ***
Comment 12 Steven Shelton 2015-11-18 18:12:23 UTC
It is an external (non-embedded) database.

I don't know that I will be able to reinstall Libo64 on this box and then test any time in the next couple of days, but I will try.
Comment 13 Alex Thurgood 2015-11-19 13:55:02 UTC
(In reply to Steven Shelton from comment #12)
> It is an external (non-embedded) database.
> 
> I don't know that I will be able to reinstall Libo64 on this box and then
> test any time in the next couple of days, but I will try.

@Steven : thanks, but I still think that this is a duplicate of 93348, which seems to indicate that all external jdbc driver connections are problematic - as mentioned in the other bug report, the only way we'll be able to hunt this down if is someone somewhere with the same setup can use a debug build with symbols of the LO 64bit master build or daily build and obtain a complete backtrace from a debugger at the moment the crash occurs. Unfortunately, that is not as easy as it sounds for the majority of users.