Bug 102247 - Crash in: com::sun::star::uno::BaseReference::operator==(com::sun::star::uno::XInterface *)
Summary: Crash in: com::sun::star::uno::BaseReference::operator==(com::sun::star::uno:...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.2.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-17 21:01 UTC by gary_sitler
Modified: 2017-05-31 10:46 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["com::sun::star::uno::BaseReference::operator==(com::sun::star::uno::XInterface *)"]


Attachments
This is the file immediately after the crash and recovery (1.55 MB, application/vnd.sun.xml.base)
2016-09-20 14:32 UTC, gary_sitler
Details
database document after crash before recovery (1.55 MB, application/vnd.sun.xml.base)
2016-09-21 19:51 UTC, gary_sitler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gary_sitler 2016-09-17 21:01:10 UTC
This bug was filed from the crash reporting server and is br-d2c0d90c-31cd-44b3-9228-f7389fc25a36.
=========================================
I was attempting to remove a module (named Module1)vfrom a macro library (named Forms) in library container My Macros.  This was the only module in the library.  I had copied all of the macros to another library and wanted to remove this library.
Comment 1 Julien Nabet 2016-09-17 21:38:40 UTC
Would it be possible you attach the original file so we can try to reproduce this?

http://crashreport.libreoffice.org/stats/crash_details/d2c0d90c-31cd-44b3-9228-f7389fc25a36
Comment 2 gary_sitler 2016-09-17 22:08:52 UTC
I am sorry.  I continued to work on this application and successfully removed the library after the recovery from the crash.  I did not back up the base document, so I cannot provide the original file.
Comment 3 gary_sitler 2016-09-20 14:32:59 UTC
Created attachment 127470 [details]
This is the file immediately after the crash and recovery

The macro organizer window remained open and showed "(Not Responding)" in the title bar.  The LibreOffice Basic Macros window also remained open but unfocused.  When I clicked on the window to give it focus, it also showed the "(Not Responding)" in the title bar.  It remained behind the macro organizer window rather than popping to the front.  I don't think that this  crash gave me the option to send the crash file.
Comment 4 gary_sitler 2016-09-20 16:20:56 UTC
This crash report relates to the above comment...
crashreport.libreoffice.org/stats/crash_details/5a0bf73e-90d7-4617-87d2-1d04f406cc88
Comment 5 gary_sitler 2016-09-21 19:51:00 UTC
Created attachment 127528 [details]
database document after crash before recovery

The LibreOffice crashed again as I was using the macro organizer in an attempt to remove a module.  This time, I am able to attach the database document before recovery...
Comment 6 gary_sitler 2016-09-21 19:58:51 UTC
This is the crash report from the latest crash.  I attached the  unrecovered database document for this crash earlier.  Again the macro organizer frame and the macros frame remained displayed but were unresponsive.

crashreport.libreoffice.org/stats/crash_details/fc76ffc4-2254-49fc-8723-7fe444009274
Comment 7 Julien Nabet 2016-09-21 20:38:01 UTC
I hadn't noticed this first but in your initial description, you indicated you wanted to remove a module in "My macros".
For the test, could you rename your LO directory profile (see 
https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?

Otherwise, could you indicate what module you wanted to remove so I can try to reproduce?
(I could remove all the modules without any crash on pc Debian x86-64 with master sources updated today)
Comment 8 gary_sitler 2016-09-21 21:34:45 UTC
I am using the operating system Microsoft Windows 10 Home.  I cannot find the directories listed in the web page that you referenced.  Nor can I find the directories listed in the "Options - LibreOffice - Paths" window this opened when I selected Options from the Tools menu.  Then selected "LibreOffice" and "Paths" from the tree in the left pane. In fact, there is no AppData directory under C:\Users\Gary so many of the paths are not found on my system.  So I do not know how to rename my directory profile as you requested.

The module that I was trying to remove was in the library container Specimens.odb in the "OpenOther" library module name "Form".  This problem seems to be transient as I was able to remove the module after recovering the document.  Sorry - I know these are the toughest kind of bugs to diagnose as I have been a software developer for decades my self.
Comment 9 Julien Nabet 2016-10-10 19:28:35 UTC
About displaying LO profile, could you give a try to this http://www.bleepingcomputer.com/tutorials/show-hidden-files-in-windows-7/ ?
Comment 10 QA Administrators 2017-05-02 11:36:51 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2017-05-31 10:46:09 UTC
Dear Bug Submitter,

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-20170531