New issue
Advanced search Search tips

Issue 847837 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: May 2018
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome crashes after

Reported by sebastie...@gmail.com, May 30 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. Open Canary
2. Wait around 40 sec
3. Canary crashes

What is the expected behavior?
Canary shouldn't crash

What went wrong?
Please see OS crash report

Crashed report ID: 74d9f907-ed1f-4b29-8a03-7ae367a47b63

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes Probably previous version

Chrome version: 66.0.3359.181  Channel: canary
OS Version: OS X 10.13.4
Flash Version:
 
canary-crash-report.txt
97.6 KB View Download
Title should be "Chrome crashes after a few seconds" but i can't see how to edit my bug report?
Can confirm that 69.0.3445.0 crashes on Windows 7 x64 after ~1 minute after the start.

Comment 3 by rsesek@chromium.org, May 30 2018

Mergedinto: 847747
Status: Duplicate (was: Unconfirmed)
Thanks for the report. There is a new canary being built and pushed with a revert of the change that caused this crash.

Crashed Thread:        25  Chrome_HistoryThread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT

Thread 25 Crashed:: Chrome_HistoryThread
0   com.google.Chrome.framework     0x000000010889e577 syncer::ClientTagBasedModelTypeProcessor::UntrackEntityForStorageKey(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + arenastring.h:225
1   com.google.Chrome.framework     0x0000000108b94761 history::TypedURLSyncBridge::OnURLsDeleted(history::HistoryBackend*, bool, bool, std::__1::vector<history::URLRow, std::__1::allocator<history::URLRow> > const&, std::__1::set<GURL, std::__1::less<GURL>, std::__1::allocator<GURL> > const&) + string:1266
2   com.google.Chrome.framework     0x0000000108b6cbf2 history::HistoryBackend::NotifyURLsDeleted(history::DeletionInfo) + weak_ptr.h:243
3   com.google.Chrome.framework     0x0000000108b600ab history::ExpireHistoryBackend::BroadcastNotifications(history::ExpireHistoryBackend::DeleteEffects*, history::ExpireHistoryBackend::DeletionType, history::DeletionTimeRange const&, base::Optional<std::__1::set<GURL, std::__1::less<GURL>, std::__1::allocator<GURL> > >) + expire_history_backend.cc:391
4   com.google.Chrome.framework     0x0000000108b60f8e history::ExpireHistoryBackend::ExpireSomeOldHistory(base::Time, history::ExpiringVisitsReader const*, int) + optional.h:62
5   com.google.Chrome.framework     0x0000000108b61450 history::ExpireHistoryBackend::DoExpireIteration() + circular_deque.h:863
6   com.google.Chrome.framework     0x0000000107241617 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) + callback_forward.h:11
7   com.google.Chrome.framework     0x0000000107260e84 base::MessageLoop::RunTask(base::PendingTask*) + vector:639
8   com.google.Chrome.framework     0x0000000107261496 base::MessageLoop::DoDelayedWork(base::TimeTicks*) + message_loop.cc:329
9   com.google.Chrome.framework     0x00000001072622dc base::MessagePumpDefault::Run(base::MessagePump::Delegate*) + message_pump_default.cc:42
10  com.google.Chrome.framework     0x00000001072857f5 <name omitted> + run_loop.cc:108
11  com.google.Chrome.framework     0x00000001072b8a7d base::Thread::ThreadMain() + lock.h:26
12  com.google.Chrome.framework     0x00000001072e8a27 base::(anonymous namespace)::ThreadFunc(void*) + platform_thread_posix.cc:78
13  libsystem_pthread.dylib         0x00007fff662dc661 _pthread_body + 340
14  libsystem_pthread.dylib         0x00007fff662dc50d _pthread_start + 377
15  libsystem_pthread.dylib         0x00007fff662dbbf9 thread_start + 13


Confirmed 69.0.3445.0 on OSX, too. 

Crash dump seems to point at "Incorrect function" exception of some sort, and the OSX report states its a EXC_BAD_ACCESS exception.
Sry wrong version reported for Canary. I'm also currently using Version 69.0.3445.0

Sign in to add a comment