Status: Available
Owner: ----
CC: [email protected],  [email protected]
Labels: Type-Bug Pri-1 OS-All Area-BrowserUI Regression stable

New issue 7466 by [email protected]: Crash when selecting an autofill  
value using mouse
http://code.google.com/p/chromium/issues/detail?id=7466

I think this is a regression because I am pretty sure it was working last
week. Now on a trunk build if I select an auto-fill value, Chrome crashes.

Jay if there is someone else who should be CCed please do so.

Stack trace:

>       chrome.dll!WebCore::PopupListBox::acceptIndex(int index=0)  Line
865 + 0x1c bytes        C++
        chrome.dll!WebCore::PopupListBox::handleMouseReleaseEvent(const
WebCore::PlatformMouseEvent & event={...})  Line 543    C++
        chrome.dll!WebCore::PopupContainer::handleMouseReleaseEvent(const
WebCore::PlatformMouseEvent & event={...})  Line 397 + 0x44 bytes       C++
        chrome.dll!WebWidgetImpl::MouseUp(const WebMouseEvent &
event={...})  Line 85 + 0x29 bytes      C++
        chrome.dll!WebWidgetImpl::HandleInputEvent(const WebInputEvent *
input_event=0x083b5798)  Line 171       C++
        chrome.dll!RenderWidget::OnHandleInputEvent(const IPC::Message &
message={...})  Line 325 + 0x21 bytes   C++
        chrome.dll!IPC::Message::Dispatch<RenderWidget>(const IPC::Message
* msg=0x07a46340, RenderWidget * obj=0x07b9b2e8, void (const IPC::Message
&)* func=0x019b4130)  Line 141 + 0x1f bytes     C++
        chrome.dll!RenderWidget::OnMessageReceived(const IPC::Message &
msg={...})  Line 167 + 0x38 bytes       C++
        chrome.dll!MessageRouter::RouteMessage(const IPC::Message &
msg={...})  Line 39 + 0x13 bytes        C++
        chrome.dll!MessageRouter::OnMessageReceived(const IPC::Message &
msg={...})  Line 30 + 0x13 bytes        C++
        chrome.dll!RenderThread::OnMessageReceived(const IPC::Message &
msg={...})  Line 199 + 0x17 bytes       C++
        chrome.dll!IPC::ChannelProxy::Context::OnDispatchMessage(const
IPC::Message & message={...})  Line 182 + 0x1b bytes    C++
        chrome.dll!DispatchToMethod<IPC::ChannelProxy::Context,void
(__thiscall IPC::ChannelProxy::Context::*)(IPC::Message const
&),IPC::Message>(IPC::ChannelProxy::Context * obj=0x04a85368, void (const
IPC::Message &)* method=0x01952e30, const Tuple1<IPC::Message> & arg={...})
Line 393 + 0xf bytes    C++
        chrome.dll!RunnableMethod<IPC::ChannelProxy::Context,void
(__thiscall IPC::ChannelProxy::Context::*)(IPC::Message const
&),Tuple1<IPC::Message> >::Run()  Line 312 + 0x1e bytes C++
        chrome.dll!MessageLoop::RunTask(Task * task=0x07a46318)  Line 308 +
0xf bytes       C++
        chrome.dll!MessageLoop::DeferOrRunPendingTask(const
MessageLoop::PendingTask & pending_task={...})  Line 319        C++
        chrome.dll!MessageLoop::DoWork()  Line 408 + 0xc bytes  C++
        chrome.dll!base::MessagePumpForUI::DoRunLoop()  Line 208 + 0x1d
bytes   C++
        
chrome.dll!base::MessagePumpWin::RunWithDispatcher(base::MessagePump::Deleg
ate * delegate=0x050efeb4, base::MessagePumpWin::Dispatcher *
dispatcher=0x00000000)  Line 52 + 0xf bytes     C++
        chrome.dll!base::MessagePumpWin::Run(base::MessagePump::Delegate *
delegate=0x050efeb4)  Line 78 + 0x1c bytes      C++
        chrome.dll!MessageLoop::RunInternal()  Line 197 + 0x2a bytes    C++
        chrome.dll!MessageLoop::RunHandler()  Line 181  C++
        chrome.dll!MessageLoop::Run()  Line 155 C++
        chrome.dll!base::Thread::ThreadMain()  Line 159 C++
        chrome.dll!`anonymous namespace'::ThreadFunc(void *
closure=0x04a05e9c)  Line 26 + 0xf bytes        C++
        kernel32.dll!_basethreadst...@8()  + 0x37 bytes 


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to