SBIE 3.00.15 batch-processing - prob with SeaMonkey v1.1.4

[pepibua]

tzuk

With batch - procedures I keep installed software on the system in current condition.

Now the batch - test under SBIE with SeaMonkey shows a small prob:

4 URL's running, output in browser SeaMonkey only 3 Sites, then stops processing

The batch is running without probs:
when SeaMonkey is n o t sandboxed or SeaMonkey is sandboxed under SBIE 3.00.12

Please, try with your batch from thread http://www.sandboxie.com/phpbb/viewtopic.php?t=1816. Thank you.

pepibua

[tzuk]

Sorry, this time I couldn't reproduce the problem. What did you mean by SeaMonkey "stops processing" as you said, does it stop accepting URL links, or does it stop responding at all?

[pepibua]

Tzuk, thanking you for taking the time to reply. Ok, I put a finer point on it. I mean to save pains, because you could find the cause.

Now, in your (and also my) batch-bat-file are 29 URL's. With "Run sandboxed" cmd.exe should read and execute all records from the bat-file, so that all 29 sites are displayed in SeaMonkey in several tabs, tab for tab, all in all 29.

But, cmd.exe reads only 4 records (URL's) and only 3-Sites-output were displayed in browser SeaMonkey, then cmd.exe stops processing.

And, shown in ProcessExplorer (SysInternals) is process cmd.exe with Window Status "Running", as-if running, but it wont work. Cmd.exe makes no headway. The cmd.exe-window is on-screen, minute to minute, and now more than an hour. Cancel.

Remark:
SBIE v3.00.14 and v3.00.15 is tested: batch-processing is not possible, as accurately described.
In SBIE v3.00.12 there is no issue like this. So, it must happen between v...12 and ...13

pepibua

[tzuk]

Are you sure you didn't get a message similar to this one, when cmd.exe stops:

Windows cannot find the file 'http://some-url'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

I get these messages occasionally, and when I click OK, cmd.exe goes for a bit, then displays that message again. Could you be getting this message too?

But I am trying this in 64-bit Windows, so this may be a problem specific to 64-bit, and not related to your particular problem.

[pepibua]

tzuk

At last I tried to get a message in 10 test runs in succession. I used the "tzuk.bat" (your and my URL's-batch-file) containing 28 records ( not 29, sorry) under Sandboxie, batch-processing by cmd.exe "Running Sandboxed".

In nine from ten tests the cursor was standing under the last screen-printed record in the cmd.exe-window, blinking. In no case any message from cmd.exe was displayed!

But, at once after cmd.exe was reading a few records, a message appeared, now from SBIE:
"WARNING: Your mail program is about to start. Sandboxie is not configured to allow the programm direct access to your mailbox files ... blabla bla ......."
Clicked "ignore"
This time, cmd.exe could read the rest of records and SeaMonkey displayed all called sites in the browser, tab for tab, all of 28.
I didn't have this message in the same procedere under SBIE 3.00.14 or ..15 before.


pepibua

[tzuk]

To get rid of the warning, see:

http://www.sandboxie.com/phpbb/viewtopic.php?t=1795

Is this with version 3.00.16? If you suppress the Sandboxie warning about the mail program, does it work fine all the way?

[pepibua]

tzuk

To get rid of the warning, see:
http://www.sandboxie.com/phpbb/viewtopic.php?t=1795

SeaMonkey declairs itself as an all-in-one internet application suite. So SeaMonkey does a call to its mailprogram with a parameter like D:\Programme\mozilla.org\SeaMonkey\seamonkey.exe -mail.

Because of this I think the OpenFilePath-setting therefore in Sandboxie.ini like OpenFilePath=seamonkey.exe,C:\Dokumente und Einstellungen\josurf\Anwendungsdaten\Mozilla\ should be enough. So, I can't sense the meaning of this message, it shouldn't be displayed.

@Is this with version 3.00.16?

Yes, I tested today SBIE v3.00.16 with the OpenFilePath-setting above. This message was displayed after 18 records reading and 17 sites displaying.

However, I have to say, the warning appears very sporadically.

@If you suppress the Sandboxie warning about the mail program, does it work fine all the way?

When I try to supress the warning setting NEW the OpenFilePath to OpenFilePath=seamonkey.exe -mail,C:\Dokumente und Einstellungen\josurf\Anwendungsdaten\Mozilla\ the warning appears, before the browser-window is displayed, proceeding with click-ignore, browser-windows displayed. And then cmd.exe reads the first record, the second warning is displayed, proceeding with click-ignore, the site was displayed in the browser in its own tab, and so on and so forth, till the job hangs as always. The job was not done ready. Tested with SBIE v3.00.16


pepibua

[tzuk]

pepibua, sorry for not responding here earlier, but it seems we are back in a scenario where you experience errors that I can't reproduce. I suggest that for now you go back to the version that was ok for you (3.00.12 was it?) and we'll pick it up later, when I have more time.

Or maybe you can use the latest Sandboxie if you feed Seamonkey less links at once?

I will however say, that OpenFilePath accepts only the process name, so

Code: Select all

OpenFilePath=seamonkey.exe -mail,......

Is no good. The " -mail" suffix has no place there.

[pepibua]

tzuk, thanks. My OpenFilePath-declaration is without "-mail"-suffix, always. So, I shall to change at SBIE v3.00.12.

Yet still I have to make an addition at my monitoring review batch-processing-SeaMonkey-SBIE, see posting above:

I monitored the process in TaskManager, first using cmd.exe (M$ Windows) and second R.exe, a Scripinterpreter (Hintenaus, Austria).

This is was I find out:

TaskManager shows the ----------------------------------------------> Window Status

1. Run: cmd.exe runs the batch-URL-bat.file and process stops, but -----> "Running" (!?) ':shock:'
2. Run: R.exe runs the batch-URL-cmd.file and process stops and OK --> "Not responding"

Both processes were stopped. What a weird status-difference. Those TaskManager-Window Status-Outputs are not clear. And we shouldn't forget, the batch-procedere tested in both processes, once using cmd.exe (M$ Windows) and another R.exe, are running SeaMonkey-unsandboxed without probs.

And,anything else. If you are testing the URL's-batch-bat.file with SeaMonkey-sandboxed again, please try to give 2, 3, 4 runs after another on the same SeaMonkey-window. Perhaps, it make sense also on 64-bit-Windows, even if current only on 32-bit-XP-System.

So, I hope I could show you another sight of the prob, additionally, and it's possible to fix this in next time. Have a nice day.



pepibua

[tzuk]

If you are testing the URL's-batch-bat.file with SeaMonkey-sandboxed again, please try to give 2, 3, 4 runs after another on the same SeaMonkey-window

I did much more than 2, 3, 4 runs. I was even running the batch tens of times, in parallel, from a number of command prompt windows open at the same time. When I say I couldn't reproduce the problem, I really mean it.

Run: R.exe runs the batch-URL-cmd.file and process stops and OK --> "Not responding"

"Not responding" does not necessarily mean the program stopped running. However I don't fully understand about R.EXE. Were you able to work around the Sandboxie/SeaMonkey problems by using R.EXE, in spite of it being "non responsive"?

[pepibua]

When I say I couldn't reproduce the problem, I really mean it. Smile

Ok. I can live at that statement. Like I said yet, your work is estimated very much, of course me too. However, I found it needful, that you should know I observed a fresh startet SeaMonkey-job sandboxed, Sandbox emptied with Heidi-Eraser, the first batch-process with cmd.exe-sandboxed with processing the 28 URL's.batfile will pass through, at times. The following runs were stopped anywhere while reading. Meaning, the cmd.exe-window stood then on the screen and no action is detectable. It's unbelievable, but TaskManager shows this process - Window Status as "Running". When the process should not stay on the screen day by day it have to be cancelled. Principally, the same applies to processes executed with R.exe. Unlike the cmd.exe-process said TaskManager here a Window Status as "Not responding". The process also must cancelled.

Were you able to work around the Sandboxie/SeaMonkey problems by using R.EXE?

Using R.exe on my system several months, not only in relation by SeaMonkey-Batch-procedures, I don't have detect a way to have a "Workaround" to bypassing the Sandboxie/SeaMonkey probs and to handle it.

pepibua