Closed
Bug 668878
Opened 13 years ago
Closed 13 years ago
Environment extraction appears to hang (GUI is frozen until it ends)
Categories
(Mozilla QA Graveyard :: Mozmill Crowd Extension, defect)
Mozilla QA Graveyard
Mozmill Crowd Extension
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 621574
People
(Reporter: u279076, Unassigned)
Details
(Whiteboard: [testday-20110701][UX-needed])
After downloading and installing Mozmill Crowd 0.1.3 in Nightly 7.0a1 20110701, Firefox appears to hang when extracting the environment. 1) Download and install Mozmill Crowd 2) Tools > Mozmill Crowd 3) Start Test-run (prompted to select folder for environment) 4) Created ~/Development/Crowd/ as the folder 5) Environment creation process begins Result: The extraction dialog appears to hang the browser completely until the process is done. Since the browser is hung, the progress bar does not move. This might cause some people to force quit Firefox before it is done setting up the environment. Additionally, once the process completes, I noticed that an error appears in the Test-run log section of the dialog: "The log file '/home/username/Development/Crowd/testrun.log' could not be read Finally, when I click Start Test-run again, the browser hangs for a minute or so and spits out the same error about testrun.log being unreadable.
I noticed that no testrun.log file is created by the environment setup process. However, creating an empty text file called testrun.log does not appear to resolve this issue.
Did a quick peek at Error Console and there are no errors showing up...
Comment 3•13 years ago
|
||
When Firefox is run from a terminal, there is output in the terminal, while the Firefox/Crowd GUI is locked up.
Updated•13 years ago
|
Summary: Environment extraction appears to hang → Environment extraction appears to hang (GUI is frozen until it ends)
Comment 4•13 years ago
|
||
Similar set up and observation as Anthony describes. However, after deleting the contents(mozmill-env) of the previously created folder and restarting the process, it resolved the problem
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•12 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•