Comment #5 on issue 28850 by rvar...@chromium.org: Reliability failure in
the network stack
http://code.google.com/p/chromium/issues/detail?id=28850
After r33251, the crash is replaced by:
chrome_2610000!URLRequestHttpJob::NotifyHeadersComplete+0x8a
[c:\b\slave\chromium-rel-xp\build\src\net\url_request\url_request_http_job.cc
@
503]
chrome_2610000!URLRequestHttpJob::OnStartCompleted+0x4d
[c:\b\slave\chromium-rel-xp\build\src\net\url_request\url_request_http_job.cc
@ 450]
chrome_2610000!RunnableMethod<ThumbnailStore,void (__thiscall
ThumbnailStore::*)(std::map<GURL,ThumbnailStore::CacheEntry,std::less<GURL>,std::allocator<std::pair<GURL
const ,ThumbnailStore::CacheEntry>
> >
> *),Tuple1<std::map<GURL,ThumbnailStore::CacheEntry,std::less<GURL>,std::allocator<std::pair<GURL
>
> const ,ThumbnailStore::CacheEntry> > >
*> >::Run+0x17 [c:\b\slave\chromium-rel-xp\build\src\base\task.h @ 284]
chrome_2610000!MessageLoop::RunTask+0x7e
[c:\b\slave\chromium-rel-xp\build\src\base\message_loop.cc @ 321]
chrome_2610000!MessageLoop::DoWork+0x1ea
[c:\b\slave\chromium-rel-xp\build\src\base\message_loop.cc @ 443]
chrome_2610000!base::MessagePumpForIO::DoRunLoop+0x7e
[c:\b\slave\chromium-rel-xp\build\src\base\message_pump_win.cc @ 469]
chrome_2610000!base::MessagePumpWin::Run+0x40
[c:\b\slave\chromium-rel-xp\build\src\base\message_pump_win.h @ 78]
chrome_2610000!MessageLoop::RunInternal+0xc0
[c:\b\slave\chromium-rel-xp\build\src\base\message_loop.cc @ 205]
chrome_2610000!MessageLoop::Run+0x57
[c:\b\slave\chromium-rel-xp\build\src\base\message_loop.cc @ 156]
so basically:
void URLRequestHttpJob::NotifyHeadersComplete() {
DCHECK(!response_info_);
response_info_ = transaction_->GetResponseInfo();
// Save boolean, as we'll need this info at destruction time, and filters
may
// also need this info.
is_cached_content_ = response_info_->was_cached;
the transaction returns null, 'cause there is no response yet.
The problem seems to be that URLRequestHttpJob::CancelAuth() posts a task
to call OnStartCompleted without the actual transaction_ having
completed yet, so there is no response.
I don't really know why we see this crash only after r33133, but I'll
revert everything :(
--
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
