Issue 4392: Chrome: Crash Report - Stack Signature: -799B23 http://code.google.com/p/chromium/issues/detail?id=4392
Comment #3 by [EMAIL PROTECTED]: Another instance... The full crash report details can be found at: http://go/crash/reportdetail?reportid=651b165ad419b167&product=Chrome&version=0.4.154.18&signature=-9D64BC Meta information: Report ID: 651b165ad419b167 Report Time: 2008/11/13 09:07:30, Thu Uptime: 1211 sec Cumulative Uptime: 0 sec User Email: User Comments: Product Name: Chrome Product Version: 0.4.154.18 OS Name: Windows NT OS Version: 6.0.6001 Service Pack 1 CPU Architecture: x86 CPU Info: GenuineIntel family 6 model 15 stepping 11 plat: Win32 ptype: browser FAULTING_IP: chrome_6ab50000!ProtectEntry::AntiOverload+d0 [c:\b\slave\chrome-official-2\build\src\chrome\browser\url_fetcher_protect.cc @ 88] 6ad8c999 8b88c4000000 mov ecx,dword ptr [eax+0C4h] EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 6ad8c999 (chrome_6ab50000!ProtectEntry::AntiOverload+0x000000d0) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 000000c4 Attempt to read from address 000000c4 DEFAULT_BUCKET_ID: STATUS_ACCESS_VIOLATION PROCESS_NAME: chrome.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". READ_ADDRESS: 000000c4 FAULTING_THREAD: 0000106c PRIMARY_PROBLEM_CLASS: STATUS_ACCESS_VIOLATION BUGCHECK_STR: APPLICATION_FAULT_STATUS_ACCESS_VIOLATION LAST_CONTROL_TRANSFER: from 6ad8cc0d to 6ad8c999 STACK_TEXT: 0019e9f0 6ad8cc0d 06110d08 0019edd8 0019edd8 chrome_6ab50000!ProtectEntry::AntiOverload+0xd0 [c:\b\slave\chrome-official-2\build\src\chrome\browser\url_fetcher_protect.cc @ 88] 0019ea98 6b08899e 060b8ac8 6ab5bcb0 0019eb80 chrome_6ab50000!ProtectManager::Register+0x6d [c:\b\slave\chrome-official-2\build\src\chrome\browser\url_fetcher_protect.cc @ 147] 0019eb44 6ab5bcec 06110d08 009f7668 6ab5bee1 chrome_6ab50000!sqlite3ValueFromExpr+0x154 [c:\b\slave\chrome-official-2\build\src\third_party\sqlite\vdbemem.c @ 924] 0019eb80 6ab68890 00000000 01127fe8 00000000 chrome_6ab50000!MessageLoop::RemoveDestructionObserver+0x42 [c:\b\slave\chrome-official-2\build\src\base\message_loop.cc @ 143] 0019eb98 6ab68431 0019edd8 0019edd8 009b7e48 chrome_6ab50000!base::MessagePumpWin::ScheduleDelayedWork+0x5 [c:\b\slave\chrome-official-2\build\src\base\message_pump_win.cc @ 113] 0019ebb4 6ab5b9e5 009b7e48 0019edd8 0019ef60 chrome_6ab50000!std::_Tree<std::_Tmap_traits<int,std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::less<int>,std::allocator<std::pair<int const ,std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,0> >::erase+0xbf [c:\b\slave\chrome-official-2\build\src\third_party\platformsdk_vista_6_0\files\vc\include\xtree @ 793] 0019ec58 6ab5b95f 1d4f58bc 00000000 0019ef60 chrome_6ab50000!MessageLoop::MessageLoop+0x1ab [c:\b\slave\chrome-official-2\build\src\base\message_loop.cc @ 89] 0019ec90 6ab5c19d 00000001 00000000 009b7e48 chrome_6ab50000!MessageLoop::MessageLoop+0x125 [c:\b\slave\chrome-official-2\build\src\base\message_loop.cc @ 84] 0019ecac 6ad4e171 009b7e48 00000001 0019efe4 chrome_6ab50000!MessageLoop::ReloadWorkQueue+0x64 [c:\b\slave\chrome-official-2\build\src\base\message_loop.cc @ 347] 0019ef84 6ab53460 0019efb0 00000001 00f82c70 chrome_6ab50000!BrowserMain+0x9a5 [c:\b\slave\chrome-official-2\build\src\chrome\browser\browser_main.cc @ 521] 0019f0f8 01292a92 01290000 0019f5ac 00301654 chrome_6ab50000!ChromeMain+0x370 [c:\b\slave\chrome-official-2\build\src\chrome\app\chrome_dll_main.cc @ 186] 0019f5a0 765d6f6f 00ffffff 00f82c70 00000000 chrome!google_update::GoogleUpdateClient::Launch+0x19c [c:\b\slave\chrome-official-2\build\src\chrome\app\google_update_client.cc @ 96] 0019f5f8 77aea676 0019f7b8 0000000e 00000026 kernel32!BasepFillUEFInfo+0x71 0019f6b0 77ae5b87 77c243e2 00300000 00000000 ntdll!RtlUnicodeStringToAnsiString+0xa4 0019f72c 0133f854 0133f850 00000000 00306f48 ntdll!RtlpLowFragHeapAllocFromContext+0xa6f 0019f74c 77ac299e 0133f82c 00000000 00000000 chrome!ATL::_AtlWinModule+0x4 0019f760 012db911 012db944 1d4d481f 012df320 ntdll!RtlInitializeCriticalSection+0x12 0019f798 012ce171 00f80000 00000000 012ce17a chrome!ATL::CComCriticalSection::Init+0x17 [f:\sp\vctools\vc7libs\ship\atlmfc\include\atlcore.h @ 101] 0019f7dc 012df31c 0019f7f0 012ce440 0133f698 chrome!_msize+0x88 [f:\sp\vctools\crt_bld\self_x86\crt\src\msize.c @ 88] 0019f8d8 765f4911 7ffd3000 0019f924 77abe4b6 chrome!classic_locale$initializer$ 0019f8e4 77abe4b6 7ffd3000 77c24dee 00000000 kernel32!BaseThreadInitThunk+0xe 0019f924 77abe489 012c572b 7ffd3000 00000000 ntdll!__RtlUserThreadStart+0x23 0019f93c 00000000 012c572b 7ffd3000 00000000 ntdll!_RtlUserThreadStart+0x1b STACK_COMMAND: ~0s; .ecxr ; kb FOLLOWUP_IP: chrome_6ab50000!ProtectEntry::AntiOverload+d0 [c:\b\slave\chrome-official-2\build\src\chrome\browser\url_fetcher_protect.cc @ 88] 6ad8c999 8b88c4000000 mov ecx,dword ptr [eax+0C4h] FAULTING_SOURCE_CODE: 84: // Logs the new send event. 85: send_log_.push(release_time_); 86: // Drops the out-of-date events in the event list. 87: while (!send_log_.empty() && > 88: (send_log_.front() + sw <= send_log_.back())) { 89: send_log_.pop(); 90: } 91: return release_time_ - now; 92: } 93: SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: chrome_6ab50000!ProtectEntry::AntiOverload+d0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: chrome_6ab50000 IMAGE_NAME: chrome.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4919e40d FAILURE_BUCKET_ID: STATUS_ACCESS_VIOLATION_c0000005_chrome.dll!ProtectEntry::AntiOverload BUCKET_ID: APPLICATION_FAULT_STATUS_ACCESS_VIOLATION_chrome_6ab50000!ProtectEntry::AntiOverload+d0 Followup: MachineOwner Issue attribute updates: Labels: Crash-0.4.154.18 -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
