Bug 10688
| Summary: | Inspector painfuly slow when Drosera is attached | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Hrvoje Blazekovic <hrvoje> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | CLOSED WONTFIX | ||
| Severity: | Normal | CC: | danny.bloemendaal |
| Priority: | P2 | ||
| Version: | 420+ | ||
| Hardware: | Mac (PowerPC) | ||
| OS: | OS X 10.4 | ||
| Bug Depends on: | 17770 | ||
| Bug Blocks: | |||
Hrvoje Blazekovic
Open a page in web kit, inspect an element with inspector. Everything works fine. Start and attach drosera. Now selecting elements in the inspector is wery slow. I tried out what I usualy do in firefox with firebug. Select a element and step trough javascript on that element.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Timothy Hatcher
Slow because Drosera is debugging the inspector's JS also. We need a way to tell Drosera to debug just one WebView (and ignore the rest).
Alexey Proskuryakov
Confirming per the above comment.
Adam Roben (:aroben)
The situation will be improved once bug 17770 is fixed. However, we may still want a way to exclude WebViews from sending cross-process calls to Drosera about their JS execution.
Adam Roben (:aroben)
*** Bug 16534 has been marked as a duplicate of this bug. ***
Kevin McCullough
Drosera is going away and JS debugging is now happening in the WebInspector.
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.