Closed
Bug 327849
Opened 19 years ago
Closed 18 years ago
Firefox hangs when scheduled without /INTERACTIVE
Categories
(Core :: Security, defect)
Tracking
()
People
(Reporter: danswer, Assigned: dveditz)
Details
Attachments
(1 file)
|
261 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 I'd like to schedule Firefox to run on my Win XP Pro system using AT. So I figure I should do (on one line): AT 21:01 "c:\Program Files\Mozilla Firefox\Firefox.exe" http://localhost/Demos/Dev/FFfromScript/Gone2.htm This works only when there are NO instances of Firefox running (check with Windows Task Manager - Ctrl+alt+delete). If there are any instances of FF running, then FF will not access the requested page, and it hangs. To be more specific: Gone2.htm contains: <html><head><script type='text/javascript'></script> <title>Close page test</title></head> <body onload="window.close()"> This page should be gone.<br> Remember to unset dom.allow_scripts_to_close_windows via about:config</body></html> If I schedule the above inserting /INTERACTIVE right after the scheduling time, then the scheduling works as expected (regardless of prior instances). However, in that case, FF is scheduled as the current user (I am the sole user/administrator on my system) and is visible (until it closes - in the case of Gone2.htm you get a flash). When AT is used without /INTERACTIVE, then Firefox is run with a User Name of SYSTEM and is not visible. So the debugging tool I have is to check the access logs on my Apache 2 server. If there are no instances of FF active at the scheduled time, then FF will start up under SYSTEM (without being visible) and attempt to retrieve the specified page. And if the page is Gone2.htm as shown above, then FF will terminate just fine. However, if Firefox is already running under SYSTEM, then approximately nothing happens (in that there is no additional instance of FF shown, nor is the specified page accessed). If, instead, Firefox is already running under my own user name, then a new (hidden) instance of FF will be started (under the User Name of SYSTEM) and hang. In the situation where there is no prior instance of FF active and the script runs, the permissions (specifically dom.allow_scripts_to_close_windows, set to true via about:config) are being picked up from the same prefs.js file that is used when I am running FF normally. In other words, FF is looking here: C:\Documents and Settings\Peter Gabor\Application Data\Mozilla\Firefox\Profiles\cfcwst5k.default\prefs.js and not in the only other (stub => empty: only the comments saying its a Mozilla User Preferences file) prefs.js file I found at: C:\Documents and Settings\LocalService\Application Data\Mozilla\Firefox\Profiles\gi6h723a.default\prefs.js Reproducible: Always Steps to Reproduce: Expected Results: When scheduled via AT sans /INTERACTIVE, I expect FF to start up under user name SYSTEM, read prefs.js from a consistent place, and not hang. In addition, it should be possible to terminate this instance of FF without the /F switch on taskkill. In other words, the following line should terminate the SYSTEM instance of FF so that it writes out the prefs.js file: TASKKILL /IM firefox.exe or TASKKILL /PID # I have marked this as critical since there is a hang involved, though I would otherwise expect a lower severity rating. I have placed this under Security since it seems that in the case where the scheduling appears to function as expected, the User's pref file is read/written, and that could potentially be a security issue. Please recategorize as appropriate. This whole issue of scheduling may seem esoteric, but with the method outlined above, I am scheduling FF to sequence through pages using GreaseMonkey. This is the only part of the whole process that is less than professional because of all the flashes/distractions when a task is running.
|
Reporter | |
Comment 1•19 years ago
|
||
|
|
Reporter | |
Comment 2•19 years ago
|
||
To be concrete, the way to observe this problem is to first go to about:config and set dom.allow_scripts_to_close_windows to true, then bring up the Windows Task Manager up (by pressing ctrl+alt+delete), and then type the following (changing the time/path to FF as necessary) into a command window, on one line: AT 22:38 "c:\Program Files\Mozilla Firefox\Firefox.exe" http://bugzilla.mozilla.org/attachment.cgi?id=212413 If there are no other instances of FF up (including the one that you are looking at this with), then you will see in the task manager an instance of FF appear and disappear. Otherwise (the bug), you will see that there is an instance of FF that will come up under the User Name SYSTEM, and it won't go away unless you use the End Program button or TASKKILL /F on it.
|
||
Comment 3•18 years ago
|
||
command line parameters are ignored if FF already open *** This bug has been marked as a duplicate of 99828 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•