Steps to reproduce: 1. Open Webkit 2. Open Drosera and attach to webkit 3. Open this html file: <html><head><script> ( function(){ QueueNode.prototype.AddChild = function (title, input) { } } )() </script><title>Queue</title></head></html> 4. WebKit Crashes
Created attachment 10554 [details] Test case Test case from Comment #0.
I'm not seeing a crash when I follow the steps in Comment #0 with a locally-built debug build of WebKit r16342 on Mac OS X 10.4.7 (8J135) with Safari 2.0.4 (419.3). I do see that Drosera pauses every time upon loading the test page, but clicking the "Continue" button lets Safari continue running. Are you seeing a crash or a hang? If it's a crash, please post a crash log if one is generated. Thanks!
Created attachment 10558 [details] Carsh log Here's the crash log. It says the application is Safari.app, but it's really the WebKit nightly binary from WebKit-SVN-r16358.dmg
(In reply to comment #3) > Created an attachment (id=10558) [edit] > Carsh log > > Here's the crash log. It says the application is Safari.app, but it's really > the WebKit nightly binary from WebKit-SVN-r16358.dmg And you would be running this on the Leopard Developer Preview, correct? When I tried to reproduce the issue, I was running on Tiger (10.4.7).
(In reply to comment #4) > (In reply to comment #3) > > Created an attachment (id=10558) [edit] > > Carsh log > > > > Here's the crash log. It says the application is Safari.app, but it's really > > the WebKit nightly binary from WebKit-SVN-r16358.dmg > > And you would be running this on the Leopard Developer Preview, correct? When > I tried to reproduce the issue, I was running on Tiger (10.4.7). > Yes, I am running the Leopard Preview.
Created attachment 11145 [details] Fixes this.
Comment on attachment 11145 [details] Fixes this. r=me
Landed in r17128.
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.