Bug 89127 - Tools > Macros > OrganizeMacros >Libreoffice Basic crashed LibreOffice
Summary: Tools > Macros > OrganizeMacros >Libreoffice Basic crashed LibreOffice
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.4.0.0.alpha1
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-04 18:02 UTC by RickWriter
Modified: 2015-02-08 12:56 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RickWriter 2015-02-04 18:02:00 UTC
Installed first Fresh version, then removed and installed Still version. Same problem.

Windows 7 with plenty of RAM. 

When I Click Tools > Macros > OrganizeMacros >Libreoffice Basic I lose all mouse and menu control. Need to use Task Manager to close it. Problem does not occur when I go to Tools > Macros > OrganizeMacros > Python.

I have Java 7 latest version installed (750). This problem happened even with LO 4.4.0. I have tried many combinations over several days. Problem occurred as well when I was runni9ng Java 7 (210).

Problem occurs when using Macro Recorder as well. Macro recorder Stop Recording button accepts mouse click, but does not finish recording session. Then I loose control and have to go to Task Manager to start over again. 

I really want to record a few macros. I have checked Bugzilla, checked the LO website, etc. This problem seems to come and go over the years.

Please advise how I can start making macros without locking up the works.

Cheers,
RickWriter
Comment 1 Joel Madero 2015-02-04 18:32:19 UTC
Please report one bug per report (here you seem to have two...one with recording, one with organizing macros).

Also please try with a fresh profile: https://wiki.documentfoundation.org/UserProfile

For this one we'll only address the first issue (organize macros crash). That being said, I'm not on a windows machine right now so can't test -- leaving as UNCONFIRMED.
Comment 2 raal 2015-02-04 18:34:25 UTC
I can not confirm with win7
 4.4.0.3
ID build: de093506bcdc5fafd9023ee680b8c60e3e0645d7
Version: 4.5.0.0.alpha0+
Build ID: 20deac4903fc0697477e855feeff482b3da234f9
TinderBox: Win-x86@42, Branch:master, Time: 2015-01-29_23:02:41


no freeze when  Click Tools > Macros > OrganizeMacros >Libreoffice Basic
Comment 3 Buovjaga 2015-02-07 19:18:11 UTC
No freeze for me either. Setting to NEEDINFO while we wait for the results of this from the reporter: https://wiki.documentfoundation.org/User_Profile#Resolving_corruption_in_the_user_profile

Win 7 Pro 64-bit, LibO Version: 4.4.0.3
Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7
Locale: fi_FI
Comment 4 RickWriter 2015-02-08 12:47:47 UTC
Applying some of the suggestions recommended has lead me to feel the problem focuses on lock files placed when a crash occurs. Here is a rough sequence of events:

1-I created a macro that ended up unresponsive after I experimented with debugging tools. I stopped the macro by terminating LibreOffice via the Windows Task Manager. It would appear that this set a ~lock file on LO or some portion of it.

2-Upon restarting the program, things seemed normal until I again started to experiment with my macro. Every time I opened the macro organizer the program froze. 

3-Following information obtained on various websites, updated Java as well as LibreOffice, to no avail.

4-I filed the bug report.

5-In response to comments, I refined my Google search, changed hidden files to visible, changed the name of my LO profile so as to force LI to create a new one for me, sought out and deleted various lock files, and learned to terminate LO more gently by using the Windows Task Manager to stop Soffice processes rather than the LO application. 

6-These steps have allowed me to work in LO once again. 

Thank you for your assistance.

Cheers,

Rick Lehtinen
Comment 5 Buovjaga 2015-02-08 12:56:03 UTC
Thank you very much for testing! I will close this report as INVALID (for lack of a better status name).