Bug 44260 - Crash after inactivity/switch to other program
Summary: Crash after inactivity/switch to other program
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-29 01:15 UTC by Marc Kaulisch
Modified: 2012-08-31 10:03 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Taskmanager Test Account - no crash (122.84 KB, image/jpeg)
2012-01-07 02:50 UTC, Marc Kaulisch
Details
Tasmanager Work Account - Crash (102.07 KB, image/jpeg)
2012-01-07 02:51 UTC, Marc Kaulisch
Details
Differences between user (crash) and user-new (no crash) in user\config path (13.28 KB, text/plain)
2012-01-11 05:40 UTC, Marc Kaulisch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Kaulisch 2011-12-29 01:15:54 UTC
My way to reproduce it: I experienced it twice on Win 7 64bit
start LODev Writer either over Start or Desktop
LO creates an empty untitled new document - and Writer symbol appears on taskbar
leave Writer to Nightly (Firefox)
Writer symbol disappears from taskbar within under a minute after switched to Nightly (Firefox)
minimizing Nightly shows a not responding Writer crash reporter
Comment 1 Cor Nouws 2011-12-29 01:25:53 UTC
Hi Marc,
thanks for reporting !
I cannot reproduce this on Win7 32nits in Virtual box. 
Doing some random work with it, other apps ... no crashes as for now.

Cor
Comment 2 Marc Kaulisch 2011-12-29 01:52:19 UTC
I tested the other applications: The only program parts that are not effected by the bug are Calc and Draw
Impress and Formula are crashing after switching to other programs as well

The crash appears even when parts of LO are present on the screen (so it looks like it is not a background/display problem) and another program is in the foreground


Other open programs are: Thunderbird, Skype, Nokia N8 and Songbird
Virus program: Microsoft Security Essentials
Comment 3 Marc Kaulisch 2011-12-29 02:05:30 UTC
even disabling the only extension that is not standard (Endnote X4 extension) does not help: Writer crashes
Comment 4 Petr Mladek 2012-01-05 05:21:57 UTC
I am not able to reproduce it with LO-.3.5.0-beta2 on Windows XP SP3 i586.
I wonder if it happens only on 64-bit system or if it happens only on your particular setup.

Macr, could you please check whether the process soffice.bin or soffice.exe shows some CPU activity or increasing memory usage in the "Windows Task Manager" [Ctrl-Alt-Del] before it freezes?
Comment 5 Marc Kaulisch 2012-01-05 21:29:09 UTC
So I tested it again. Still Writer crashes.
The first time today I registered only rundll32 to be additionally active before the crash
the seconnd time soffice.bin had up to 49% CPU shortly before the crash (might also because the unexpected error warning from LODev arrives...
Comment 6 Marc Kaulisch 2012-01-06 00:37:50 UTC
This is disappointing. I tested it on a Windows Server 2008 R2 Standard 64bit.
I cannot reprodice it there. I do not get LibDev Writer to crash in the way I get it back home.
So I will reinstall the LibDev version at home and will see if the installation process was not correct or what ever...
Comment 7 Cor Nouws 2012-01-06 01:40:42 UTC
(In reply to comment #6)
> This is disappointing. 

Depends how you look at it. It might help finding the source of the problems..

> So I will reinstall the LibDev version at home and will see if the installation
> process was not correct or what ever...

Maybe there are other things that need to be reinstalled.
Do I remember correct that I advised you to try with a clean user profile too?
Thanks for your testing efforts!
Comment 8 Marc Kaulisch 2012-01-07 02:30:15 UTC
Win7 64bit:
I uninstalled LODev 3.5 beta 2. I created a new admin user (Test) and installed LODev (for any user on this computer). I restarted Win afterwards:

My Test-User does not experience a crash in the way I found with my work user.
Following the TaskManager I see that soffice.bin has a higher CPU load about 10-20 seconds after the start of LODev Writer. But with Test-User it does not crash!

Logging off from Test user and starting my work user: With Start/All-Programs/LODev/LODev Writer Writer crashes as described in my first post!

But if I use the shortcut on the desktop I do not experience a crash.

To sum up: Something breaks soffice.bin shortly after its launch and only if a certain shortcut to launch LODev is activated.
New user accounts do not seem to be affected.
Comment 9 Marc Kaulisch 2012-01-07 02:50:40 UTC
Created attachment 55234 [details]
Taskmanager Test Account - no crash

These processes are open while on the new Test user account. No crash when starting LODev Impress over Start/Programs/LODev.
Comment 10 Marc Kaulisch 2012-01-07 02:51:56 UTC
Created attachment 55235 [details]
Tasmanager Work Account - Crash

These processes are open while on the old work user account. Crashes when starting LODev Impress over Start/Programs/LODev.
Comment 11 Petr Mladek 2012-01-09 02:48:35 UTC
Marc, do you have installed any LO extensions for the user Marc? Could you please try to remove them?

If it does not help. Could you please try to rename the current user configuration? Please, read hints at http://wiki.documentfoundation.org/UserProfile

I have it in the directory C:\Documents and Settings\pmladek\Application Data\
LibreOffice\3.

Note that the directory "Application Data" is hidden, so it is not visible by default. You need to enable showing hidden files to see it.

Also please, make sure that the processes soffice.bin and soffice.exe are not running when renaming the directory.
Comment 12 Marc Kaulisch 2012-01-09 12:14:19 UTC
Petr,
as tested the other extension used does not harm or change the behavior.

After renaming the User Profile, LODev 3.5 does not crash anymore as experienced  before.

But after my first start LODev crashes as described in this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=43989

The second start works well.
Comment 13 Petr Mladek 2012-01-10 00:49:17 UTC
It would be interesting to investigate what exact setting caused the crash. I wonder if any of the Windows experts have an idea how to get better debug information.

Anyway, the problem seems to be somehow specific to your system. We have got it working. It should not block the release, so I lower the severity a bit.
Comment 14 Marc Kaulisch 2012-01-11 05:39:00 UTC
I did a review of the two configurations: user (crashes) and user-new (does not crash)
I found three major differences in three paths:
1) user\registrymodifications.xcu differs
2) user\extensions\ differs in terms of an tmp-path
3) user\config - crashing user has a lot more files in this path

Have a look at differences in attached file diffs_config.txt
Comment 15 Marc Kaulisch 2012-01-11 05:40:08 UTC
Created attachment 55430 [details]
Differences between user (crash) and user-new (no crash) in user\config path
Comment 16 Petr Mladek 2012-01-12 05:24:54 UTC
I am not sure if I understand the diff correctly. I see this diff format for the first time. Also it does not help that it is in German ;-)

My understanding is that the left 3 columns describe the old (broken) configuration and the 3 columns on the right describe the new (working) configuration.

Also, I guess that the word "keine" means that the file in missing.


So, one big difference is that the new configuration does not include javasettings_Windows_x86.xml. It might mean that Java is disabled, some functionality is not used. I wonder if some java stuff might trigger the crash again if you configure it.

Another difference is that the new configuration includes just en-US config files. The old configuration included localized config files for "de", "en-GB", "en-ZA". I am not sure if this could make any difference, though.


One "easy" test might be if you use the working configuration, copy the missing files there and try to run LO. It would be great if you could do it in two steps. Just copy the java configuration in the first stage (or configure it via Tool/Options/LibreOffice/Java). Then you could copy the missing *.so? files in the second test round.
Comment 17 Marc Kaulisch 2012-01-12 12:19:46 UTC
Tested Beta3:
Uninstalled LODev beta2. Deleted User-ProFile. Restarted Win7.
No crash when Beta 3 used like beta2.

Looks to be solved by the workaround - recreate new user-profile - hope this does not affect too many Windows users.

Anyway, I still can confirm https://bugs.freedesktop.org/show_bug.cgi?id=43989
Comment 18 Petr Mladek 2012-01-13 05:05:49 UTC
I am afraid that we can't do much if we are not able to reproduce it. So, I close this bug for now.

Feel free to reopen it if you see it again in the future.
Comment 19 Marc Kaulisch 2012-02-16 23:08:16 UTC
After my installation of 3.5 over the 3.4.5. This bugs seems to reappear. I tested it now with Writer and Impress. Both crash after a short while.

At least for Writer it looks like Writer is stable after it is launched after the crash.
Very annoying...
Comment 20 Petr Mladek 2012-02-17 01:30:16 UTC
Does it help you to run LO with fresh user configuration?

IMPORTANT: Please, do not remove the old configuration. Just rename the directory. Also, please stop LO before you do this. Make sure that soffice processes are not in the task manager.

If it helps, could you please zip the old and the new configuration and attach it here?
Comment 21 Florian Reisinger 2012-08-14 13:57:11 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 22 Florian Reisinger 2012-08-14 13:58:34 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 23 Florian Reisinger 2012-08-14 14:03:06 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 24 Florian Reisinger 2012-08-14 14:05:21 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 25 Marc Kaulisch 2012-08-15 10:41:56 UTC
I cannot reproduce it with LO 3.6 anymore. Looks like it was one of the problems with the user settings.