simple cache crash in Cronet tests |
|
Issue descriptionChrome Version: 67.0.3389.0 OS: Android https://ci.chromium.org/buildbot/tryserver.chromium.android/android_cronet_tester/3591 C 227.894s Main [ FAILED ] org.chromium.net.urlconnection.CronetHttpURLConnectionTest#testGetResponseHeaderFieldWithPosExceed (CRASHED) If you download the 33 MB logcat you'll see: fe56b: 04-04 22:15:35.599 14403 14418 I TestRunner: started: testGetResponseHeaderFieldWithPosExcee ... fe56b: 04-04 22:15:35.679 14403 14426 F chromium: [0404/221535.683342:FATAL:simple_entry_impl.cc(622)] Check failed: state_ == STATE_UNINITIALIZED || state_ == STATE_FAILURE. If you look at the symbolicated stack traces you'll find: Stack Trace: RELADDR FUNCTION FILE:LINE 0018a229 logging::LogMessage::~LogMessage() ../../base/logging.cc:594:29 002541fd disk_cache::SimpleEntryImpl::~SimpleEntryImpl() ../../net/disk_cache/simple/simple_entry_impl.cc:622:3 002542d5 disk_cache::SimpleEntryImpl::~SimpleEntryImpl() ../../net/disk_cache/simple/simple_entry_impl.cc:619:37 v------> scoped_refptr<disk_cache::EntryImpl>::Release(disk_cache::EntryImpl*) ../../base/memory/scoped_refptr.h:280:8 0023a379 scoped_refptr<disk_cache::EntryImpl>::~scoped_refptr() ../../base/memory/scoped_refptr.h:208:0 v------> std::__ndk1::__tuple_leaf<0u, scoped_refptr<disk_cache::SimpleEntryImpl>, false>::~__tuple_leaf() ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/tuple:170:7 v------> std::__ndk1::tuple<scoped_refptr<disk_cache::SimpleEntryImpl> >::~tuple() ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/tuple:474:0 002517cb base::internal::BindState<void (disk_cache::SimpleEntryImpl::*)(), scoped_refptr<disk_cache::SimpleEntryImpl> >::~BindState() ../../base/bind_internal.h:723:0 002517b7 base::internal::BindState<void (disk_cache::SimpleEntryImpl::*)(), scoped_refptr<disk_cache::SimpleEntryImpl> >::Destroy(base::internal::BindStateBase const*) ../../base/bind_internal.h:726:5 v------> scoped_refptr<base::internal::BindStateBase>::Release(base::internal::BindStateBase*) ../../base/memory/scoped_refptr.h:280:8 0017248f scoped_refptr<base::internal::BindStateBase>::~scoped_refptr() ../../base/memory/scoped_refptr.h:208:0 001724cf scoped_refptr<base::internal::BindStateBase>::operator=(base::internal::BindStateBase*) ../../base/memory/scoped_refptr.h:223:36 001c275f base::(anonymous namespace)::PostTaskAndReplyRelay::~PostTaskAndReplyRelay() ../../base/threading/post_task_and_reply_impl.cc:51:16 v------> std::__ndk1::__tuple_leaf<0u, base::(anonymous namespace)::PostTaskAndReplyRelay, false>::~__tuple_leaf() ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/tuple:170:7 v------> std::__ndk1::tuple<base::(anonymous namespace)::PostTaskAndReplyRelay>::~tuple() ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/tuple:474:0 v------> base::internal::BindState<void (*)(base::(anonymous namespace)::PostTaskAndReplyRelay), base::(anonymous namespace)::PostTaskAndReplyRelay>::~BindState() ../../base/bind_internal.h:723:0 001c2887 base::internal::BindState<void (*)(base::(anonymous namespace)::PostTaskAndReplyRelay), base::(anonymous namespace)::PostTaskAndReplyRelay>::Destroy(base::internal::BindStateBase const*) ../../base/bind_internal.h:726:0 v------> scoped_refptr<base::internal::BindStateBase>::Release(base::internal::BindStateBase*) ../../base/memory/scoped_refptr.h:280:8 0017248f scoped_refptr<base::internal::BindStateBase>::~scoped_refptr() ../../base/memory/scoped_refptr.h:208:0 0018e805 base::internal::IncomingTaskQueue::TriageQueue::Clear() ../../base/message_loop/incoming_task_queue.cc:176:3 0018f7c1 base::MessageLoop::DeletePendingTasks() ../../base/message_loop/message_loop.cc:380:40 00190513 base::MessageLoop::~MessageLoop() ../../base/message_loop/message_loop.cc:93:5 0018f85f base::MessageLoop::~MessageLoop() ../../base/message_loop/message_loop.h:408:19 v------> std::__ndk1::default_delete<base::MessageLoop>::operator()(base::MessageLoop*) const ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/memory:2233:5 v------> std::__ndk1::unique_ptr<base::MessageLoop, std::__ndk1::default_delete<base::MessageLoop> >::reset(base::MessageLoop*) ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/memory:2546:0 v------> std::__ndk1::unique_ptr<base::MessageLoop, std::__ndk1::default_delete<base::MessageLoop> >::~unique_ptr() ../../third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/memory:2500:0 001c4691 base::Thread::ThreadMain() ../../base/threading/thread.cc:363:0 001c24d1 base::(anonymous namespace)::ThreadFunc(void*)
,
Apr 9 2018
> Is that one of the tests covered by the instructions here Yes.
,
Apr 9 2018
Hmm, can't reproduce this after a few hundred runs (will keep trying, and will also do so on a different device). Did you see this more than once? Any info on state of other threads? It's possible the best I can do from this is improve the check logging...
,
Apr 9 2018
> Did you see this more than once? No, just saw it once on https://chromium-review.googlesource.com/c/chromium/src/+/984114/7 > Any info on state of other threads? I didn't see any other thread state. You're free to look at the bot run I liked to.
,
May 3 2018
|
|
►
Sign in to add a comment |
|
Comment 1 by morlovich@chromium.org
, Apr 9 2018