Issue metadata
Sign in to add a comment
|
[Assert] heap_profiling::`anonymous namespace'::HookZeroInitAlloc edit bugs&comments |
||||||||||||||||||||||
Issue descriptionCrash report : https://goto.google.com/cbvhc Report IDd5a3da26b5fa7894 Product, versionChrome_Android, 69.0.3493.4 Process typebrowser Magic Signature[Assert] heap_profiling::`anonymous namespace'::HookZeroInitAlloc edit bugs&comments Stable Signaturebase::debug::`anonymous namespace'::DebugBreak-495f8cbaedit bugs&comments Report TimeMon, 23 Jul 2018 18:06:34 GMT Process uptime31 min, 11 sec, 215 ms Client ID4b5080da3ca7478db69ca34d82bf114c FilesminidumpDownloadReprocess this minidump In shutdownfalse Device ModelBlade S6 Magic Stack with stack quality at 5% : Thread 0 (id: 0x46c6) CRASHED [SIGABRT @ 0x000046c6 ] MAGIC SIGNATURE THREAD Stack Quality5%Show frame trust levels 0xb6f1db04 (libc.so + 0x00038b04 ) 0xb6ef942d (libc.so + 0x0001442d ) 0xb6ef5c67 (libc.so + 0x00010c67 ) 0x2751c25c (dalvik-main space (deleted) + 0x1491c25c ) 0xb6ef41ae (libc.so + 0x0000f1ae ) 0xa35c4473 (libchrome.so -debugger_posix.cc:228 ) base::debug::(anonymous namespace)::DebugBreak() 0xa35c4457 (libchrome.so -debugger_posix.cc:258 ) base::debug::BreakDebugger() 0xa39a8cc7 (libchrome.so -lock_impl_posix.cc:104 ) base::internal::LockImpl::Lock() 0x615f6c6e 0x30312861 (dalvik-main space (deleted) + 0x1d712861 ) 0x7461461e (dalvik-alloc space (deleted) + 0x00fc361e ) 0x726f7270 (system@framework@boot.oat + 0x02375270 ) 0x20676e67 (dalvik-main space (deleted) + 0x0da76e67 ) 0x20757045 (dalvik-main space (deleted) + 0x0db57045 ) 0x746e6f61 (dalvik-alloc space (deleted) + 0x01095f61 ) 0xa44bd8ff (libchrome.so -allocator_shim.cc ) heap_profiling::(anonymous namespace)::HookZeroInitAlloc(base::allocator::AllocatorDispatch const*, unsigned int, unsigned int, void*) This is new regression which started on Chrome M69 and first observed on 69.0.3452.0, On latest Chrome Dev on Android this is top#16 browser crash with 54 crash reports from 48 clients. Please find crash impact on chrome versions here : https://goto.google.com/ettjk
,
Jul 25
erikchen@ would you help triage or investigate this issue?
,
Jul 25
Every 32-bit arm stack with base::debug::BreakDebugger is broken and meaningless. https://bugs.chromium.org/p/chromium/issues/detail?id=851851
,
Jul 25
If you look at the raw stack data in the dump (e.g. with minidump_stackwalk -s, or just by viewing it by hand if you can work out how to decode it) then you can expect to see the LOG(FATAL) message that was printed that is the actual crash reason, on the stack - that *will* point to the true cause, but it may well just be an existing crash we already know about by another, less broken, magic signature. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pbomm...@chromium.org
, Jul 23Components: Internals