Issue 113155 - soffice.bin stops responding.
Summary: soffice.bin stops responding.
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 3.1.1
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: writerneedsconfirm
QA Contact: issues@sw
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2010-07-15 07:46 UTC by kpalagin
Modified: 2010-07-15 14:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
screenshot (76.01 KB, image/png)
2010-07-15 07:48 UTC, kpalagin 		no flags Details
problematic file (57.53 KB, application/msword)
2010-07-15 07:50 UTC, kpalagin 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description kpalagin 2010-07-15 07:46:44 UTC 
At random OpenOffice ceases to work and every attempt to start any app just
causes new pair or soffice.bin and soffice.exe to appear in task list (see
screenshot). The only way to get openoffice work again is to kill soffice.bin
that has hung.
This started couple of years ago (maybe more) and now I have repro:
1. using OO3.1.1 open attached .docx - OO will crash and display notification.
Click OK.
2. now try opening any other file or any OO application - it would not open and
all you get are more soffice.bin and soffice.exe pairs in task list.

Please note that crash itself is fixed in m75, so you have to use version 3.1.1
to see how soffice stops responding.
Comment 1 kpalagin 2010-07-15 07:48:19 UTC 
Created attachment 70622 [details]
screenshot
Comment 2 kpalagin 2010-07-15 07:50:39 UTC 
Created attachment 70623 [details]
problematic file
Comment 3 Olaf Felka 2010-07-15 07:52:06 UTC 
Please try this with OOo 3.2.1? OOo 3.1.1 is pretty outdated. As you have
written this won't happen in m75....
Comment 4 kpalagin 2010-07-15 09:32:29 UTC 
3.2.1 does not crash and as such does not hung.
I beleive that investigating post-crash hung is worthwhile and would like you to
not close this issue, but instead assign it to relevant developer.

Thanks&regards.
KP.
Comment 5 Olaf Felka 2010-07-15 09:43:54 UTC 
I don't think that a developer will spend time to investigate in a crash that is
history.
Comment 6 eric.savary 2010-07-15 09:57:31 UTC 
@kpalagin: if this is fixed/doesn't happen anymore in a current build, there is
no reason to take action on this.
Comment 7 eric.savary 2010-07-15 09:58:04 UTC 
Closed
Comment 8 kpalagin 2010-07-15 10:26:59 UTC 
The problem I am trying to describe is soffice's behavior after crash.
I am sure that behavior is not fixed and this behavior is common enough for my
50 users that I am asking to investigate that.

Éric, Olaf,
please try reproducing the hung and tell if the hung (not crash) is expected.
This is going to take just 5 minutes of your time.
Comment 9 michael.ruess 2010-07-15 13:21:31 UTC 
I even cannot reproduce the crash in OOo 3.1.1 opening the attached docx.
But referring to the "hung" - I think that this was caused by the bug in the
filter leading to the crash in OOo.
Comment 10 kpalagin 2010-07-15 14:17:09 UTC 
Michael,
thanks for your reply. My problem is that hung - it happens quite often and
requires either manually killing soffice.bin processes or rebooting. So far I
had no reliable way of reproducing the hung. But if you can't repro the crash
then there is not much you can do to debug the hung.

WBR,
KP.