Bug 89283

Summary: Clicking on File in the menu bar, locks program up for a couple of minutes
Product: LibreOffice Reporter: zak <izak.legrange>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: ilmari.lauhakangas
Priority: medium    
Version: 4.4.0.3 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description zak 2015-02-10 09:50:41 UTC
When I click File in the menu bar the program locks up for a couple of minutes. It affects all the programs Calc,Writer and Draw. All the other options in the menu bar work like normal, it is only File causing a problem. It seems to be only on Windows7sp1 I am seeing this

Tried complete reinstall with cleaning the registry, did not work

Windows Event viewer gives the following
- System 

  - Provider 

   [ Name]  Application Hang 
 
  - EventID 1002 

   [ Qualifiers]  0 
 
   Level 2 
 
   Task 101 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2015-02-10T08:55:10.000000000Z 
 
   EventRecordID 81320 
 
   Channel Application 
 
   Computer AZA-PC086.eu.autoliv.int 
 
   Security 
 

- EventData 

   soffice.bin 
   4.4.0.3 
   18f0 
   01d0450ede4ad745 
   0 
   C:\Program Files (x86)\LibreOffice 4\program\soffice.bin 
   82e7cfc7-b102-11e4-b298-b4b52fcb5f9c 
   55006E006B006E006F0077006E0000000000 


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 006E0055 006E006B 0077006F 0000006E 
0008: 0000    


In Bytes

0000: 55 00 6E 00 6B 00 6E 00   U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00   o.w.n...
0010: 00 00                     ..
Comment 1 Buovjaga 2015-02-10 10:39:47 UTC
Try this first: https://wiki.documentfoundation.org/User_Profile#Resolving_corruption_in_the_user_profile

If the problem persists, you can take a shot at getting a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Set to NEEDINFO.
Change back to UNCONFIRMED after coming back to this.
Comment 2 zak 2015-02-10 10:51:55 UTC
Resolving corruption in the user profile fixed the problem. You can close the bugreport. 

Thanks for the help
Comment 3 Buovjaga 2015-02-10 11:16:18 UTC
Thank you for reporting and testing!