Run an OpenOffice 2.4.1 product sandboxed. There are two running processes in the sandbox, soffice.exe and soffice.bin.
Close the OO product, both processes remain running and will not terminated - each time you have to do it manually.

Open the sbie gui and include soffice.exe and soffice.bin under 'lingering programs'. Hopefully this should help.

Already tried it before, didn't help.

Specifying LingerProcess to end processes will only work under specific circumstances. From the Sandboxie Q&A's:
"LingerProcess will not terminate a process, if that process was the first process launched in the sandbox."

So if a sandboxed program runs OpenOffice (sandboxed), then LingerProcess will kill those two processes if they are the last ones running in the sandbox. However, if you launch OpenOffice sandboxed yourself, such as by using "Run Sandboxed", then LingerProcess will not help you. Those 2 processes always remain in memory after you run OpenOffice unsandboxed, just as they remain when you intentionally run the program sandboxed. It's just that it's more noticeable that they are still in memory, when the red dots remain in Sandboxie's tray icon.

@FAQ: I already know about this


If I run an OO product unsandboxed, both processes disappear in the task manager after closing OO ... but not if OO was started sandboxed.

Sorry. I overlooked the fact that the Quickstarter program starts with Windows on my computer, and that's why those processes stay in memory for me. Otherwise, I've never had those 2 stay in Sandboxie's list of processes if another sandboxed program is what started the OpenOffice program. They are listed as LingerProcess in my Sandbox Settings. I never run OpenOffice sandboxed, manually.

I get the same behavior as Ruhe.
XP Pro SP3

I just tried openoffice portable and see the same problems sandboxed as Ruhe (and MitchE323).

Thanks for confirmations.

I guess I'm missing something here. Doesn't this apply to how you're starting Oo:
"LingerProcess will not terminate a process, if that process was the first process launched in the sandbox."

There are plenty of processes that linger in the sandbox. In addition to those two, some that I have in my config. are acrord32.exe, jusched.exe, syncor.exe, wuauclt.exe, realsched.exe, leechget.exe, pdfprohook.exe, and the latest that tzuk apparently added: trustedinstaller.exe.

They will all Linger in the sandbox. All of them will be terminated if they were started by a program that is running sandboxed:
if you have your email program running sandboxed, and you open an attachment using Oo, then those two sandboxed Oo processes will be killed after all of the other programs in the sandbox end.
If you choose to run Oo sandboxed yourself, as in "Run Sandboxed", then LingerProcess will not stop those two processes, as stated in the quoted passage above.

LingerProcess only applies to child processes, thats right.
Thats not the problem here.
It makes no difference if soffice.bin and/or soffice.exe are defined as LingerProcess, in both cases they won't be ended if OO was started as a master process (not as a child) ... but they should.

There may be something of a problem relating to Mem Usage. Checking the Task Manager, the soffice.bin is calling on an amount about twice that of explorer.exe. The numbers are fairly consistent whether sandboxed or not. That seems high to me, as all I have open is the writer. It is also about 8-9 times higher than Microsoft Word (winword.exe).

When I "Run Sandboxed" Oo 'Writer':
Using Process Monitor to monitor swriter.exe, soffice.exe, and soffice.bin

The first process that runs is soffice.exe.
Later, soffice.exe opens soffice.bin.
Then still later, soffice.bin opens swriter.exe.

So from what I can determine, since soffice.exe is the first process to start, specifying it in a LingerProcess setting will not help to close it when Writer is closed - as expected.

But whats the correct way to prevent the described behaviour now?

Just tried 3.31.04 and OpenOffice 3.0 ... ... did anyone found a working configuration?