To reproduce: - open the attached html file - hover the mouse over "Mouse Over" link - Select the "Select" link in the popup box - move mouse away so that popup disappears - press Ctrl C - crash
Created attachment 20539 [details] Testcase
Created attachment 20540 [details] Fixes the crash described in the bug.
<rdar://problem/5863412>
Comment on attachment 20540 [details] Fixes the crash described in the bug. Internally, we haven't been able to reproduce this. But the null check is fine (and its done earlier in the function too). Is there a way to make a layout test for this?
I can reproduce this 100% of the time but the steps are a little tricky. After mouse over, you need to jump quickly to the popup box and then select the dummy link using mouse. Now move mouse away (without clicking) so that popup disappears and pressing ctrl-c at that time causes crash. I am trying to write layout test for this.
I am also able to reproduce this 100% of the time To be clear, on Mac Os X you need to type "cmd-c" instead of "ctrl-c". To re-iterate the repro steps: (1) Mouse over the link called "Mouse Over" (2) Quickly move the mouse into the yellow box (otherwise it closes before you reach it) (3) Drag a selection around the "Select" word (4) Move the mouse outside of yellow box and it will be dismissed (5) If on mac os x, type cmd-c (copy) else if on windows type ctrl-c (copy) (6) Results in crashes in safari 3.1 Raised priority since it is a crash.
Created attachment 20655 [details] Crash log for kuchal's repro steps
Created attachment 20669 [details] Layout test I have this layout test case which is rather complicated. I couldn't reduce it any further because there are multiple steps involved and making even any small changes renders the test useless by causing the crash to go away. If this layout test is acceptable let me know and I will generate a patch for it.
Comment on attachment 20540 [details] Fixes the crash described in the bug. Clearing the review flag since this patch was landed.
r33583 It's great to try to work on a test case for this, but the bug is fixed so this should be closed. If you want an open bug to track the work, then it should be a separate bug report.