Bug 17554
| Summary: | [Drosera] Windows build hangs Safari when page is navigated | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brett Fattori <bfattori> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | CLOSED DUPLICATE | ||
| Severity: | Major | CC: | aroben, kmccullough |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
Brett Fattori
When I start Drosera, then the nightly build of webkit, as soon as I navigate to a page containing javascript Safari just sits in a "hung" state. If I close Drosera, Safari resumes operation as normal.
Drosera properly identifies the scripts that are actionable, but it doesn't allow for any debugging. Drosera is responding, but Safari acts as if it is waiting for a callback to return before continuing. The display in Safari does not refresh, either.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Roben (:aroben)
This behavior is due to JS execution being extremely slow while Drosera is attached. See bug 17770.
*** This bug has been marked as a duplicate of 17770 ***
Timothy Hatcher
Closing since Drosera has been replaced by the new Web Inspector debugger. Moving to the New Bugs component so the Drosera component can be closed and removed.