New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 662227 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Nov 2017
Cc:
rsesek@chromium.org
█ shrike@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Allocator instrument causes Chrome/Chromium to crash on 10.12.1

Project Member Reported by erikc...@chromium.org, Nov 3 2016 
Allocator instrument causes Chrome/Chromium to crash. Works fine on 10.11.6. Leak and time profile instruments work fine on 10.12.1.

Xcode: 8.1
SIP: Disabled
macOS: 10.12.1

Chrome crash server id: a1875b7900000000
instruments_allocator_instrument_crash.txt
59.4 KB View Download

Comment 1 by erikc...@chromium.org, Nov 3 2016

Status: Available (was: Untriaged)
https://crash.corp.google.com/browse?q=reportid=%27a1875b7900000000%27#0

Thread 8 CRASHED [EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE @ 0x0000700006c3c7a8 ] MAGIC SIGNATURE THREAD

0x0000000105920e8d	(liboainject.dylib + 0x00000e8d )	
0x0000000105920f50	(liboainject.dylib + 0x00000f50 )	
0x0000000105922662	(liboainject.dylib + 0x00002662 )	
0x00007fffb1adc511	(libsystem_malloc.dylib + 0x00004511 )	malloc_zone_calloc
0x00007fffb1adce2e	(libsystem_malloc.dylib + 0x00004e2e )	calloc
0x00007fff9c814348	(CoreFoundation + 0x0000e348 )	__rehashd
0x00007fff9c8141ff	(CoreFoundation + 0x0000e1ff )	-[__NSDictionaryM setObject:forKey:]
0x000000010924ad41	(Google Chrome Framework -platform_thread_mac.mm:187 )	base::PlatformThread::SetCurrentThreadPriority(base::ThreadPriority)
0x000000010924b297	(Google Chrome Framework -platform_thread_posix.cc:63 )	base::(anonymous namespace)::ThreadFunc(void*)
0x00007fffb1b6faaa	(libsystem_pthread.dylib + 0x00003aaa )	_pthread_body
0x00007fffb1b6f9f6	(libsystem_pthread.dylib + 0x000039f6 )	_pthread_start
0x00007fffb1b6f220	(libsystem_pthread.dylib + 0x00003220 )	thread_start
0x000000010924b27f	(Google Chrome Framework + 0x018a827f )
Project Member

Comment 2 by sheriffbot@chromium.org, Nov 6 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by spqc...@chromium.org, Nov 7 2017 

[mac bug triage] Is this still an issue?

Comment 4 by patricia...@chromium.org, Nov 29 2017

Status: Archived (was: Untriaged)
[mac bug triage]

Going ahead and closing this, it doesn't seem actionable at the moment since the crash has expired.
►

Sign in to add a comment