Steps to reproduce Crash 1. Download latest nighty build r45883 for window platform. 2. Run safari browser and open the URL http://maps.google.co.in/maps?hl=en&tab=wl 3. Click and drags on images on maps and it will crashed Call stack during crash is as follows > WebKit.dll!WebDragClient::willPerformDragSourceAction(WebCore::DragSourceAction action=DragSourceActionImage, const WebCore::IntPoint & intPoint={...}, WebCore::Clipboard * clipboard=0x7fbf51c0) Line 120 + 0x6 bytes C++ > WebKit.dll!WebCore::DragController::startDrag(WebCore::Frame * src=0x7fef5680, WebCore::Clipboard * clipboard=0x7fbf51c0, WebCore::DragOperation srcOp=DragOperationNone, const WebCore::PlatformMouseEvent & dragEvent={...}, const WebCore::IntPoint & dragOrigin={...}, bool isDHTMLDrag=false) Line 662 C++ > WebKit.dll!WebCore::EventHandler::handleDrag(const WebCore::MouseEventWithHitTestResults & event={...}) Line 2256 + 0x35 bytes C++ > WebKit.dll!WebCore::EventHandler::handleMouseDraggedEvent(const WebCore::MouseEventWithHitTestResults & event={...}) Line 406 + 0xe bytes C++ > WebKit.dll!WebCore::EventHandler::handleMouseMoveEvent(const WebCore::PlatformMouseEvent & mouseEvent=, WebCore::HitTestResult * hoveredNode=) Line 1371 + 0xc bytes C++ > WebKit.dll!WebViewWndProc(HWND__ * hWnd=0x00000003, unsigned int message=4077521261, unsigned int wParam=3, long lParam=-1475735342) Line 2058 + 0x10 bytes C++ 00010011()
I ran into this today, so it's still 100% reproducible in r47289. Dragging _any_ content in any web page seems to crash.
Ping. This is still happening, two months after the bug was reported.
I cannot reproduce this issue. I am using the latest nightly r48354. I followed the instructions given by xpert as well as tried dragging random objects (including text and graphics) on http://www.apple.com and dropping them into the Apple search text box. I tested this using a VMware instance of Windows XP Pro w/SP 3 using two virtual processors and 3 GB of RAM. Jen and xpert, if this is still occurring for you when using the latest nightly, can you elaborate further on how to trigger this crash? (In reply to comment #2) > Ping. This is still happening, two months after the bug was reported.