Updates:
Summary: Crash in IPC::Channel::ChannelImpl::CreatePipe(std::string
const&, IPC::Channel::Mode) calling DebugUtil::BreakDebugger()
Comment #61 on issue 26754 by [email protected]: Crash in
IPC::Channel::ChannelImpl::CreatePipe(std::string const&,
IPC::Channel::Mode) calling DebugUtil::BreakDebugger()
http://code.google.com/p/chromium/issues/detail?id=26754
The old summary: "Chrome crash :
AppCacheDispatcherHost::Initialize(IPC::Message::Sender*, int, int)"
Since r33351/r33353, this crash has moved. It will now show up in
DebugUtil::BreakDebugger() called by
IPC::Channel::ChannelImpl::CreatePipe(std::string const&,
IPC::Channel::Mode). It's
also moved from the browser process to the renderer process. A sad tab is
better
than a crashed browser.
As I wrote in comment 60, in the renderer process, on the first recvmsg()
on the
channel to the plugin process returns 0, indicating that the other end of
the pipe is
closed. I don't see any reason for it to be returning 0, though.
This may be an OS bug.
--
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
