Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 OS-All Area-Misc New issue 19592 by antonmuhin: Unexpected (?) NULL proxy in V8CustomEventListener::callFunction http://code.google.com/p/chromium/issues/detail?id=19592
Chrome Version : 3.0.196.0 URLs (if applicable) : According to http://crash/reportdetail? reportid=19d99906cbceb8a7&product=Chrome&version=3.0.196.0&date=&signature= WebCore::V8Proxy::callFunction(v8::Handle Chrome could crash when invoking callFunction on NULL proxy. The 'fix' for that was landed into WebKit (check proxy before invoking callFunction): https://bugs.webkit.org/show_bug.cgi?id=27883 , but ideally it should be investigated why we have NULL here in the first place. Couple of things to notice: 1) code is invoked from updater (see callstack partially quoted below): 0x0201a1bf [chrome.dll - renderer_main.cc:148] RendererMain(MainFunctionParams const &) 0x01c336fa [chrome.dll - chrome_dll_main.cc:504] ChromeMain 0x00402ba1 [chrome.exe - google_update_client.cc:96] google_update::GoogleUpdateClient::Launch(HINSTANCE__ *,sandbox::SandboxInterfaceInfo *,wchar_t *,char const *,int *) 0x7c82ffff [kernel32.dll + 0x0002ffff] CreateFiberEx 2) we already have NULL proxy check in destructor (added when V8CustomEventListener.cpp was added by David Levin, http://trac.webkit.org/changeset/41600). -- 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 -~----------~----~----~----~------~----~------~--~---
