RESOLVED WORKSFORME 53155
REGRESSION: plugins/destroy-on-setwindow.html fails on Leopard 
https://bugs.webkit.org/show_bug.cgi?id=53155
Summary REGRESSION: plugins/destroy-on-setwindow.html fails on Leopard
Ryosuke Niwa
Reported 2011-01-25 19:08:06 PST
plugins/destroy-on-setwindow.html has been crashing on the Leopard bots with the following assertion failure: ASSERTION FAILED: [self currentWindow] (/Volumes/Big/WebKit-BuildSlave/leopard-intel-debug/build/Source/WebKit/mac/Plugins/WebNetscapePluginView.mm:565 void -[WebNetscapePluginDocumentView restorePortState:](WebNetscapePluginDocumentView*, objc_selector*, OpaquePortState*)) I went through all the logs on build.webkit.org but it has been crashing as far as we have the log and couldn't figure out the revision from which it regressed.
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2011-01-25 19:23:39 PST
<rdar://problem/8917076>
Alexey Proskuryakov
Comment 2 2012-04-18 11:36:36 PDT
Are there still any bots seeing this? Doesn't happen for me locally on Lion.
Tony Chang
Comment 3 2012-04-26 13:30:57 PDT
(In reply to comment #2) > Are there still any bots seeing this? Doesn't happen for me locally on Lion. The test is in platform/mac-leopard/Skipped and platform/wk2/Skipped. It might still be crashing on Leopard.
Tony Chang
Comment 4 2012-04-26 13:37:01 PDT
(In reply to comment #3) > (In reply to comment #2) > > Are there still any bots seeing this? Doesn't happen for me locally on Lion. > > The test is in platform/mac-leopard/Skipped and platform/wk2/Skipped. It might still be crashing on Leopard. Actually, maybe we can just delete platform/mac-leopard now. I'll file a bug for that. I suspect this is still crashing on Chromium Mac Leopard, but we probably have a separate bug for that.
Ryosuke Niwa
Comment 5 2012-04-26 13:57:18 PDT
(In reply to comment #4) > Actually, maybe we can just delete platform/mac-leopard now. I'll file a bug for that. I suspect this is still crashing on Chromium Mac Leopard, but we probably have a separate bug for that. Yes: http://code.google.com/p/chromium/issues/detail?id=69571
Note You need to log in before you can comment on or make changes to this bug.