Issue metadata
Sign in to add a comment
|
Chrome Mac Crash - net::ChannelIDService::GetChannelID |
||||||||||||||||||||||
Issue descriptionChrome Version: 69.0.3453.0 OS: 10.13.4 (17E202) What steps will reproduce the problem? (1) Launch canary Expected: Actual: Canary crashes. See the symbolized crash dump. What is the expected result? Canary launches. What happens instead? Canary crashes. See the attached file with the symbolized crash. Note that no crash reports were created for this crash in /Users/borisv/Library/Application Support/Google/Chrome Canary, so we may not see this crash at all. Thread 3 Crashed:: Chrome_IOThread 0 com.google.Chrome.framework 0x0000000108c4531a net::ChannelIDService::GetChannelID(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::unique_ptr<crypto::ECPrivateKey, std::__1::default_delete<crypto::ECPrivateKey> >*, base::RepeatingCallback<void (int)> const&, net::ChannelIDService::Request*) + channel_id_service.cc:289 1 com.google.Chrome.framework 0x0000000107858378 extensions::MessagePropertyProvider::GetChannelIDOnIOThread(scoped_refptr<base::TaskRunner>, scoped_refptr<net::URLRequestContextGetter>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> const&) + message_property_provider.cc:73 2 com.google.Chrome.framework 0x000000010785874e base::internal::Invoker<base::internal::BindState<void (*)(scoped_refptr<base::TaskRunner>, scoped_refptr<net::URLRequestContextGetter>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> const&), scoped_refptr<base::SingleThreadTaskRunner>, scoped_refptr<net::URLRequestContextGetter>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> >, void ()>::RunOnce(base::internal::BindStateBase*) + scoped_refptr.h:207 3 com.google.Chrome.framework 0x000000010885f3d7 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) + callback_forward.h:11 4 com.google.Chrome.framework 0x000000010887f8b4 base::MessageLoop::RunTask(base::PendingTask*) + vector:639 5 com.google.Chrome.framework 0x000000010887fd88 base::MessageLoop::DoWork() + message_loop.cc:373 6 com.google.Chrome.framework 0x000000010890e454 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + message_pump_libevent.cc:210 7 com.google.Chrome.framework 0x00000001088a3f05 <name omitted> + run_loop.cc:137 8 com.google.Chrome.framework 0x0000000107122814 content::BrowserProcessSubThread::IOThreadRun(base::RunLoop*) + browser_process_sub_thread.cc:0 9 com.google.Chrome.framework 0x00000001088d4e2d base::Thread::ThreadMain() + lock.h:26 10 com.google.Chrome.framework 0x000000010890cc17 base::(anonymous namespace)::ThreadFunc(void*) + platform_thread_posix.cc:78 11 libsystem_pthread.dylib 0x00007fff6080a661 _pthread_body + 340 12 libsystem_pthread.dylib 0x00007fff6080a50d _pthread_start + 377 13 libsystem_pthread.dylib 0x00007fff60809bf9 thread_start + 13
,
Jun 8 2018
,
Jun 8 2018
Are you able to reproduce this with a build of Chromium on your mac (I haven't been able to do so, but this might be specific to your profile or an extension)? If so, does the issue go away if you revert https://chromium-review.googlesource.com/c/chromium/src/+/1089859? I have no idea why that change would cause this crash, but it is related to Channel ID and first appeared in 69.0.3453.0.
,
Jun 8 2018
I got confused by the reported version at the top of the bug report and the actual version that crashed in attached file. The crash was of 68.0.3426.0, not 69.0.3453.0.
,
Jun 8 2018
No, I grabbed wrong crash report from the system's diagnostic reports. My bad. rsesek@ is correct. Sorry about the confusion. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rsesek@chromium.org
, Jun 8 2018Labels: Stability-Crash OS-Mac