This bug was filed from the crash reporting server and is br-79ecb678-c319-4134-8df7-dc0c2fe8db0d.
I am using LibreOffice Base with a MySQL-Backend.
Especially when trying to view/use a Form, LibreOffice crashes very often with this report.
- MySQL 5.7.23 connected over WAN
Steps to reproduce:
1. Design Database with SQL Backend
2. Create Form for one table
3. Open Form (not in Design Mode)
4. Likely observer random crash.
I'd really like to help to get this resolved, but I am not sure which information might be relevant to add.
If you need any further info, or more crash reports (I can provide plenty), I'll gladly add them to this bug report. I also have a Visual Studio debugger and gdb (MingW) at hands, if that might help any further.
Thanks for your help!
Using the same connector (mysql-connector-java-8.0.15.jar), but with MariaDB 5.5.63 on localhost, I don't have that problem.
If it can help....
Version: 126.96.36.199 (x64)
Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3
Threads CPU : 4; OS : Windows 10.0; UI Render : par défaut;
Locale : fr-FR (fr_FR); Calc: group threaded
This problem seems to happen only on Windows 10 for me and my wife, when she was working with Ubuntu just now (same connector), it didn't crash at all.
I've noticed the crashes mostly when I was editting a form, saving it and then tried to view it.
Some more crash reports (somewhat older, but they are always the same nonetheless):
(In reply to Alexander Steinhöfer from comment #2)
> This problem seems to happen only on Windows 10 for me and my wife, when she
> was working with Ubuntu just now (same connector), it didn't crash at all.
Which Java-version is running on Windows and on Ubuntu?
$ java --version
openjdk 10.0.2 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4, mixed mode)
C:\> java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
On Windows, the Java Control Panel tells me, that that's the latest JRE available.
I could install Java 11 JDK and try it again, if you think that could be helpful (although, I guess, most users would be on the latest JRE)!
@Alexander : from the trace you have provided via the crash reporter, several exceptions appear to be caught at lines 806 (explicit catch test for obtaining MetaData from the db), 813 (test for whether the ESCAPE PROCESSING PROPERTY has been set, and 814 (explicit catch test) in SingleSelectQueryComposer.cxx
Reading the comment at line 796 of that same file, which refers to an OOo bug for Access:
and from Ocke's comments at the time :
I'm guessing that the corresponding LO MetaData.cxx code needs adjusting somehow to present the correct sequence, however, there are quite a few of these in the LO source code, so I'd hasard a guess and say it might be :
in this particular instance, as your connection is JDBC and you mentioned you were trying to open a form (which is a Writer document).
You don't say what your form is based on, and whether or not it contains subforms, as this would help pinpoint the issue further.
Additionally, the mysql ConnectorJ/8.x series is known to produce a number of buggy behaviours currently with LO, so perhaps switching back to a 5.x series might provide a workaround for the time being.
I would add that if Ocke's comments from the OOo bug are anything to go by, then in relation to the 8.x ConnectorJ driver, the blame game as to whether it is a LO code problem or a Mysql code problem needs to be solved in some way...suffice it to say that Oracle have no real incentive to be concerned about bugs with their drivers in LO, unless the effects are more general and extend to other Java applications ;-)
I also encountered with same problem. As I search for the problem there are many suggestions but not worked any of it.
Great; But still Search engine more Great https://www.google.com/
Following this topic around, and hoping your include more source to be more convincing and broad[url=https://www.google.com/]![/url]
Thanks for reporting this issue.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Alexander Steinhöfer,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Alexander Steinhöfer,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker