Issue 62312 - killing soffice.exe must kill soffice.bin too
Summary: killing soffice.exe must kill soffice.bin too
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: All Windows, all
: P4 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: regression
: 39390 (view as issue list)
Depends on:
Reported: 2006-02-20 10:52 UTC by kai.sommerfeld
Modified: 2013-08-07 15:34 UTC (History)
4 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description kai.sommerfeld 2006-02-20 10:52:13 UTC
soffice.bin is just an implementation detail. The only official program entry
point is soffice.exe. If somebody wants to start soffice, all that needs to be
done is to exec soffice.exe. Thus, it should be enough to kill soffice.exe if an
offcie instance shall be terminated. Currently, the office does not really die
in case soffice.exe gets killed, because soffice.bin stays alive. An again,
soffice.bin is just an implementation detail that should not be revealed to the

Actually, introduction of soffice.bin has broken functionality of the OfficeBean.
Comment 1 kai.sommerfeld 2006-02-20 14:01:10 UTC
Setting to OOo 2.0.2
Comment 2 hennes.rohling 2006-02-20 17:14:20 UTC
During DLL initialization of SAL the current process is attached to the parent 
process if the parent process id (and only this one, faking does not work) will be 
supplied be environment variable ATTACHED_PARENT_PROCESSID.

The office lodaer wrapper sets this environment variable.
Comment 3 hennes.rohling 2006-02-20 17:15:46 UTC
Comment 4 hennes.rohling 2006-02-21 11:34:50 UTC

re-open issue and reassign to
Comment 5 hennes.rohling 2006-02-21 11:34:54 UTC
reassign to
Comment 6 hennes.rohling 2006-02-21 11:34:57 UTC
reset resolution to FIXED
Comment 7 Olaf Felka 2006-02-21 13:35:12 UTC
of: killing soffice.exe kills soffice.bin -> verified. Mozilla and ActiveX
plugin is still working
Comment 8 stephan_schaefer 2006-02-22 08:19:52 UTC
ssa: code review done - looks good!
Comment 9 Olaf Felka 2006-02-23 09:28:22 UTC
Comment 10 Olaf Felka 2006-03-15 13:30:54 UTC
OF: Is ok in m159
Comment 11 Olaf Felka 2006-07-20 12:54:08 UTC
The behaviour of the office has to be reworked.
Comment 12 Olaf Felka 2006-07-20 13:01:25 UTC
This fix leads to a problem with the lock file in the user layer. Logging out
from windows  with a running quickstarter leaves this lock file. In OOo 2.0.2 
we have removed this file.
Comment 13 carsten.driesner 2006-07-20 14:17:49 UTC
cd: Added mba on CC.
Comment 14 hennes.rohling 2006-08-07 10:32:05 UTC
Comment 15 hennes.rohling 2007-02-12 11:53:43 UTC
Comment 16 Martin Hollmichel 2008-01-25 16:52:23 UTC
set target to 3.0
Comment 17 kai.sommerfeld 2008-06-30 14:17:03 UTC
hro: no time to fix this for 3.0. Sorry, need to re-target to 3.1.
Comment 18 kai.sommerfeld 2008-07-23 14:31:31 UTC
*** Issue 39390 has been marked as a duplicate of this issue. ***
Comment 19 Graham Perrin 2008-10-11 13:32:00 UTC
Referring myself from issue 81536

Behaviour of Mac OS X 10.5.4 may be troublesome if it finds difficulty with a connected WebDAV server. I have a 
vague sense that troublesome behaviours may be worsened by the relatively strange way in which OOo 3.0.0rc1 
responds to a force quit (with or without a forced unmount of the associated volume). 

A highlight from where I initially (but not later) suspected an issue limited to WebDAV 
service from Plone: 

> once, earlier, my computer froze completely whilst the application/connection were in that state

Although complete freezes (distinct from logged panics) may be extraordinarily rare, *if* there any is any 
association with behaviour of OOo processes *then* I should encourage fixing/improving sooner rather than 

Whilst I can't contribute code, I'm fairly well prepared to test in a Mac OS X environment. 
Comment 20 hennes.rohling 2008-10-15 13:47:01 UTC
@grahamperrin: Please don't mix up completely different issues. This results in
confusion when reading the issue comments.
Comment 21 Graham Perrin 2008-10-21 16:44:07 UTC
@hro and all other readers: for any confusion, sorry. I guessed (incorrectly) a possible relationship 
between the two tickets.
Comment 22 hennes.rohling 2009-01-21 10:10:17 UTC
Actually there's no real usecase for this.
Comment 23 hennes.rohling 2009-01-21 10:25:25 UTC
Comment 24 kai.sommerfeld 2011-03-30 09:30:22 UTC
To recap the actual regression:

"Introduction of soffice.bin has broken functionality of the OfficeBean"

To recap the problem with the original fix:

"This fix leads to a problem with the lock file in the user layer. Logging out
from windows  with a running quickstarter leaves this lock file. In OOo 2.0.2 
we have removed this file."

cd: As the actual problem seams to be framework-related, please take over.