search

qchbai / gperftools

Automatically exported from code.google.com/p/gperftools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

TCMalloc crash on Windows using Chrome M14 extension process #367

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Got an access violation accessing location 0x3239312f.  The following is the 
stack trace.  The exception happened in one of the extension process.

Windows Version: 7
Chrome Version: M14.0.835

    chrome.dll!tcmalloc::SLL_Next(void * t=0x3239312f)  Line 44 + 0x3 bytes C++
    chrome.dll!tcmalloc::SLL_Pop(void * * list=0x006e0394)  Line 58 + 0xb bytes C++
    chrome.dll!tcmalloc::ThreadCache::FreeList::Pop()  Line 209 + 0x9 bytes C++
    chrome.dll!tcmalloc::ThreadCache::Allocate(unsigned int size=128, unsigned int cl=9)  Line 346  C++
    chrome.dll!`anonymous namespace'::do_malloc(unsigned int size=128)  Line 1168 + 0x10 bytes  C++
    chrome.dll!malloc(unsigned int size=128)  Line 126 + 0x9 bytes  C++
    chrome.dll!generic_cpp_alloc(unsigned int size=128, bool nothrow=false)  Line 16 + 0x9 bytes    C++
    chrome.dll!operator new(unsigned int size=128)  Line 28 + 0xb bytes C++
    chrome.dll!NewRunnableMethod<IPC::ChannelProxy::Context,void (__thiscall IPC::ChannelProxy::Context::*)(IPC::Message const &),IPC::Message>(IPC::ChannelProxy::Context * object=0x01ea4000, void (const IPC::Message &)* method=0x55f8c100, const IPC::Message & a={...})  Line 368 + 0xa bytes C++
    chrome.dll!IPC::ChannelProxy::Context::OnMessageReceivedNoFilter(const IPC::Message & message={...})  Line 114 + 0x31 bytes C++
    chrome.dll!IPC::SyncChannel::SyncContext::OnMessageReceived(const IPC::Message & msg={...})  Line 321   C++
    chrome.dll!IPC::Channel::ChannelImpl::ProcessIncomingMessages(base::MessagePumpForIO::IOContext * context=0x01eec004, unsigned long bytes_read=352)  Line 284 + 0x19 bytes  C++
    chrome.dll!IPC::Channel::ChannelImpl::OnIOCompleted(base::MessagePumpForIO::IOContext * context=0x01eec004, unsigned long bytes_transfered=352, unsigned long error=0)  Line 375 + 0x10 bytes   C++
    chrome.dll!base::MessagePumpForIO::WaitForIOCompletion(unsigned long timeout=4294967295, base::MessagePumpForIO::IOHandler * filter=0x00000000)  Line 514 + 0x1b bytes  C++
    chrome.dll!base::MessagePumpForIO::WaitForWork()  Line 493  C++
    chrome.dll!base::MessagePumpForIO::DoRunLoop()  Line 477 + 0x8 bytes    C++
    chrome.dll!base::MessagePumpWin::RunWithDispatcher(base::MessagePump::Delegate * delegate=0x0271f8b0, base::MessagePumpWin::Dispatcher * dispatcher=0x00000000)  Line 51 + 0xf bytes    C++
    chrome.dll!base::MessagePumpWin::Run(base::MessagePump::Delegate * delegate=0x0271f8b0)  Line 80 + 0x1c bytes   C++
    chrome.dll!MessageLoop::RunInternal()  Line 451 + 0x2a bytes    C++
    chrome.dll!MessageLoop::RunHandler()  Line 425  C++
    chrome.dll!MessageLoop::Run()  Line 349 C++
    chrome.dll!base::Thread::Run(MessageLoop * message_loop=0x0271f8b0)  Line 129   C++
    chrome.dll!base::Thread::ThreadMain()  Line 164 + 0x16 bytes    C++
    chrome.dll!base::`anonymous namespace'::ThreadFunc(void * params=0x01e901a0)  Line 37 + 0xf bytes   C++

Original issue reported on code.google.com by kumar.vi...@gmail.com on 14 Sep 2011 at 6:37

GoogleCodeExporter commented 9 years ago 
This almost always -- well, always in our experience, but I don't want to be so 
absolute :-) -- means memory corruption in the application.  (Memory corruption 
can cause crashes in one memory allocator even if it works perfectly fine in 
another.)  If you can, try using tcmalloc_debug, or valgrind, or similar to see 
what's going on.

I'm closing this bug Invalid because it's almost certainly not a problem with 
tcmalloc, but feel free to reopen if you can track this down to a problem in 
tcmalloc.

Original comment by csilv...@gmail.com on 14 Sep 2011 at 8:37