Bug 44351 - LibreOffice 3.4.4 crashes on event "Open Document" at close from macro execution
Summary: LibreOffice 3.4.4 crashes on event "Open Document" at close from macro execution
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: x86 (IA32) Windows (All)
: low normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-31 08:49 UTC by Peter Zimmerer
Modified: 2013-11-27 15:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
ZIP Archive with the described files (1.01 KB, application/zip)
2011-12-31 08:49 UTC, Peter Zimmerer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zimmerer 2011-12-31 08:49:29 UTC
Created attachment 55009 [details]
ZIP Archive with the described files

The crash does only occur in LibreOffice 3.4.4. It does not occur in version 3.3.4. I can reproduce it for LibreOffice 3.4.4 on Windows XP 32 Bit and on Windows Vista 64 Bit as well.

In order to reproduce the issue please proceed as follows:

Enter the attached basic macro (file onOpenDocument.bas from attached ZIP archive) via "Tools -> Macros -> Organize Macros -> LibreOffice Basic..." as a (global) standard macros.

Assign this macro to event "Open Document" saved in area "LibreOffice".

Create a small csv file with file extension ".csv".

Now open this file with LibreOffice Calc, enter the proper setting on the "Text Import ..." dialog, and press OK on the following msgbox popup. This will successfully close LibreOffice according to the macro code in version 3.3.4 but will crash in version 3.4.4. More precisely, the system show the "LibreOffice Document Recovery" popup with description "Due to an unexpected error, LibreOffice crashed. ...". Sometimes Windows sends a popup with an application error. The recorded entry from Vista application event log is also attached.
Comment 1 Joel Madero 2012-06-18 13:15:24 UTC
I am unable to reproduce this bug with 3.6 in Linux. Going to mark as NEEDINFO. Can you try to reproduce it in a more recent release and let me know if it still exists, if it does we'll open it back up.
Comment 2 QA Administrators 2013-05-29 23:05:08 UTC
Dear Bug Submitter,

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

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!


Warm Regards,
QA Team
Comment 3 QA Administrators 2013-07-08 21:22:22 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO