Apache OpenOffice (AOO) Bugzilla – Issue 62312
killing soffice.exe must kill soffice.bin too
Last modified: 2013-08-07 15:34:42 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 'customer'. Actually, introduction of soffice.bin has broken functionality of the OfficeBean.
Setting to OOo 2.0.2
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.
.
. re-open issue and reassign to of@openoffice.org
reassign to of@openoffice.org
reset resolution to FIXED
of: killing soffice.exe kills soffice.bin -> verified. Mozilla and ActiveX plugin is still working
ssa: code review done - looks good!
retargeted
OF: Is ok in m159
The behaviour of the office has to be reworked.
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: Added mba on CC.
set target to 3.0
hro: no time to fix this for 3.0. Sorry, need to re-target to 3.1.
*** Issue 39390 has been marked as a duplicate of this issue. ***
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 http://dev.plone.org/plone/ticket/8478 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 later. Whilst I can't contribute code, I'm fairly well prepared to test in a Mac OS X environment.
@grahamperrin: Please don't mix up completely different issues. This results in confusion when reading the issue comments.
@hro and all other readers: for any confusion, sorry. I guessed (incorrectly) a possible relationship between the two tickets.
Actually there's no real usecase for this.
Retargeted.
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.