Bug 44426 - Repeated use of style modify crashes OS
Summary: Repeated use of style modify crashes OS
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.3.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-03 10:48 UTC by John Fisher
Modified: 2012-08-31 10:05 UTC (History)
1 user (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 John Fisher 2012-01-03 10:48:33 UTC
When going through the styles popup, in this case looking for certain fonts, I repeatedly picked a new style without closing the modify dialog box. This appeared to create a stack of dialogs ( there was a strange heavy shadow, but no cascading view) and eventually ( maybe 25 styles) locked up my system, forcing a hard reboot.
Comment 1 Petr Mladek 2012-01-05 04:41:10 UTC
I am unable to reproduce this with LO-3.4.5-rc2-x86_64 on SLED11-SP1. I do not see any extensive CPU or memory usage.

I know that it is a bit painful because it reboots the system. Though, are you able to reproduce this?

It is possible that the problem is not caused by the many dialogs but with a particular style or font. If you are able to reproduce this, please, try to remember what style or font you selected just before the crash.

BTW: LO-3.3 is pretty old. We do not longer provide bug fix releases for this code base. You might consider to switch to LO-3.4.4. Note that LO-3.4.5 is going to be available the following week.

Hmm, this looks like a corner case. It is hard to reproduce and not so common scenario => can't block the release => lovering the severity a bit.
Comment 2 John Fisher 2012-01-05 09:47:42 UTC
Understand your changes. 3.3.4 is the latest for Ubuntu Natty, which is only one release behind.

Will try to reproduce on another machine. This original one is too busy to crash again :)

one clarification: I was looking for styles, and clicking "modify" on styles, without canceling the previous dialog box ( I couldn't see it ). The font I was looking for was Courier10pitch, but mostly I wasn't finding it, so the font was Arial, Times New Roman, or CourierNew - the standard MS fonts.
Comment 3 Florian Reisinger 2012-08-14 14:00:08 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 4 Florian Reisinger 2012-08-14 14:01:17 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 5 Florian Reisinger 2012-08-14 14:06:01 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 6 Florian Reisinger 2012-08-14 14:08:02 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