Bug 72502

Summary:	Installing LibreOfficeDev 4.2.0.0.beta2 affects LibreOffice 4.1.3.2's performance
Product:	LibreOffice	Reporter:	severoraz
Component:	LibreOffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cno
Priority:	medium
Version:	4.2.0.0.beta2
Hardware:	Other
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:

Description severoraz 2013-12-09 02:50:48 UTC

Steps to reproduce:
1. Install LibreOffice 4.1.3.2.
2. Install LibreOfficeDev 4.2.0.0.beta2.
3. Open LibreOffice and edit any Style. This should be flawless. Close the application.
4. Open LibreOfficeDev and edit any Style. In my case, the application froze for some seconds and then the style edit window appeared. Close the application.
5. Open LibreOffice again and edit any Style. In my case, now LibreOffice had inherited the freezing time witnessed in step 4.

Comment 1 Cor Nouws 2013-12-09 07:46:10 UTC

Hi Wolter,

thanks for reporting this problem.
Quite odd, to be honest.

Is there any change that both installations use the same user profile?
Or that the thing is solved after restart of your OS?
What OS do you have?

Maybe you can get help - in you have answers on those- from any of the user support channels in LibreOffice
  http://www.libreoffice.org/get-help/

regards,
Cor

Comment 2 severoraz 2013-12-09 14:37:13 UTC

Oh sorry, I forgot to write how I solved the problem and that other relevant info you ask for. I am using Ubuntu 13.10 amd64. To solve the problem I will continue the steps I wrote before on comment #0 (description):

6. Remove LibreOfficeDev and reboot the computer.
7. Repeat step 3 again. The freezing time should be gone.

This was what solved my problem. Before this I tried both restarting LibreOffice and rebooting the computer and trying LibreOffice, but nothing was solved. 

The next thing that occurred to me was that maybe LibreOfficeDev was sharing some new faulty file with LibreOffice and so I tried removing LibreOfficeDev. This was successful after a reboot.

Comment 3 Cor Nouws 2013-12-10 18:23:19 UTC

Hi Wolter,

OK, great, thanks for that additional info. Then prolly there was something odd in the installation?
We can keep an eye on it, for if more occurences pop up?!

For now, most logic is if I close this as WorksForMeAndYou.

regards,
Cor

Comment 4 severoraz 2013-12-11 00:54:31 UTC

Sorry, I forgot to answer one of your questions.

I can't directly evidence that the installation did or didn't use my settings, but I don't think so since the settings were all default in the dev. version.

I guess it's right if we wait for more occurrences :)