Bug 108948 - Crash using UNO java to show dialog and close document afterwards (vcl::Window::SetWindowPeer())
Summary: Crash using UNO java to show dialog and close document afterwards (vcl::Windo...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: sdk (show other bugs)
Version:
(earliest affected)
5.2.7.2 release
Hardware: x86 (IA32) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-04 14:53 UTC by msiko
Modified: 2019-05-08 20:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["vcl::Window::SetWindowPeer(com::sun::star::uno::Reference<com::sun::star::awt::XWindowPeer>,VCLXWindow *)"]


Attachments
Minimal Example Program (4.08 KB, text/plain)
2017-07-04 14:53 UTC, msiko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description msiko 2017-07-04 14:53:37 UTC
Created attachment 134479 [details]
Minimal Example Program

This bug was filed from the crash reporting server and is br-bb006f30-81ad-485a-92f4-dbdbf103222d.
=========================================

Crash occurs only on Windows.

I attached a short program which reproduces the crash.
Just open a quickstart.exe which accepts connections from UNO.
Start the program and repeatedly close the Dialog and afterwards the document.
The remote bridge does not crash on every try, but on every 2nd try at least on my system and on those of my colleagues.
Comment 1 Xisco Faulí 2017-07-27 23:13:55 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
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.
Comment 2 msiko 2017-07-28 07:11:43 UTC
Crash still occurs with latest version:
http://crashreport.libreoffice.org/stats/crash_details/3b6dc0b6-fec6-4844-a057-ab795292dcee
Comment 3 raal 2018-07-27 15:08:33 UTC
How should I run your program?
Tried
java CrashExample.java
Error: Could not find or load main class CrashExample.java
Comment 4 msiko 2018-09-18 13:13:00 UTC
Sorry for not including the instructions.

1. Copy file into a folder called "crashexample" and add the LibreOffice jars.
2. Change to the "crashexample" directory
3. Compile with "javac -cp *;. CrashExample.java"
4. Run with "java -cp *;. crashexample.Crashexample"

Tried to reproduce the problem again with LibreOffice 6.0.6 and it did not crash. Seems to be fixed.
Comment 5 Xisco Faulí 2018-09-18 13:53:44 UTC
The crash signature is only reproducible in 5.2.* -> http://crashreport.libreoffice.org/stats/signature/vcl::Window::SetWindowPeer(com::sun::star::uno::Reference%3Ccom::sun::star::awt::XWindowPeer%3E,VCLXWindow%20*)

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.
Comment 6 QA Administrators 2019-03-21 11:11:54 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2019-05-08 20:28:54 UTC
Dear msiko,

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp