Steps to reproduce: 1. Open URL in Safari: http://www.t-com.de 2. Start Drosera and attach to Safari. 3. Click "reload" on the www.t-com.de web page. Expected results: The page should reload in under a minute (or less). Actual results: The page takes 3-5 minutes to reload (ball-park estimate; did not time it). Notes: Tested with locally-built WebKit r15455 and Safari 2.0.4 (419.3) on Mac OS X 10.4.7 (8J135/PowerPC).
Actually, it doesn't matter if it's a reload or an initial load--both take a long time to complete.
Created attachment 9469 [details] Example image 1
Created attachment 9470 [details] Example image 2
Comment on attachment 9469 [details] Example image 1 This was meant for Bug 9931.
Comment on attachment 9470 [details] Example image 2 This was meant for Bug 9931.
David, can you still reproduce this? The URL takes roughly 20 seconds to load for me with r15633 and Drosera attached, compared to around 5 seconds without Drosera.
(In reply to comment #6) > David, can you still reproduce this? The URL takes roughly 20 seconds to load > for me with r15633 and Drosera attached, compared to around 5 seconds without > Drosera. With a local DEBUG build of WebKit r15633, I let it run over 15 minutes before killing it. Drosera consumed 85-90% of the CPU the whole time it was running, and both Safari and Drosera were labeled as "not responding" off and on during that time in the Activity Monitor. I will try with a nightly build next.
My initial test was with the r15633 nightly, but a test with a debug build of WebKit r15637 and a release build in Drosera gave similar results: around 40 seconds to load. Using debug builds of WebKit in both Drosera and Safari resulted in horribly slow performance like you observed: closer to four minutes loading the page. I guess Shark or `sample' output is the next step.
Created attachment 9689 [details] Sample of Drosera using debug WebKit while attached to Safari It seems likely that the slowdown is simply due to the lack of optimisation in JSCore in debug builds of WebKit. From that point of view, it behaves as expected and is not really a bug. David, I'll let you decide what to do with this bug report.
Closing bug as RESOLVED/INVALID per Comment #9. Thanks Mark! Guess I won't be running debug versions of WebKit with Drosera anymore!
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.