The chromium crash when run monkey test
Reported by
zhicai....@longcheer.corp-partner.google.com,
Apr 23 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Steps to reproduce the problem: 1. start the monkey test tool What is the expected behavior? The Chromium run normally What went wrong? the chrome native crash. I check the log and found it crash in the native. But we don't have the source code . Pls help to analysis。Thanks a lot. The log is too large to upload chromiumbugs.So i upload on this issue. https://partnerissuetracker.corp.google.com/u/3/issues/78370642 Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 64.0.32822.137 Channel: n/a OS Version: 8.1.0 Flash Version:
,
May 16 2018
There are so many crash ID. so I save as a file This is the Chrome crash ID list in the Attachment
,
May 16 2018
Oh this is in Chromium not Chrome, so we can't get a crash id. Can you include a stack trace?
,
May 17 2018
Uploaded Crash Report ID 20f1a3db2c9a2135 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:13 AM Provide additional details Uploaded Crash Report ID f1427b79c6c6c368 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:12 AM Provide additional details Uploaded Crash Report ID b5be945ee67ab224 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:10 AM Provide additional details Uploaded Crash Report ID d9d21d9f67980ae4 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:10 AM Provide additional details Uploaded Crash Report ID be25d49dec2a7335 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:07 AM Provide additional details Uploaded Crash Report ID fa93af68b6420437 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:05 AM Provide additional details Uploaded Crash Report ID 2aca2af491dfd2b8 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:03 AM Provide additional details Uploaded Crash Report ID f076315d242f0a67 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:02 AM Provide additional details Uploaded Crash Report ID d3e268cb52fe4244 (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:31:01 AM Provide additional details Uploaded Crash Report ID ceebdc632a6dc61b (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:19:30 AM Provide additional details Uploaded Crash Report ID 460aae529733a5eb (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:19:12 AM Provide additional details Uploaded Crash Report ID 18e3e0c9d34214ba (Local Crash ID: Chrome) Crash report uploaded on Wednesday, May 16, 2018 at 9:19:04 AM
,
May 17 2018
Crash is: Thread 0 (id: 23751) CRASHED [SIGTRAP @ 0xd674da30 ] MAGIC SIGNATURE THREAD Stack Quality79%Show frame trust levels 0xd7929334 (libmonochrome.so -profile_destroyer.cc:131 ) ProfileDestroyer::~ProfileDestroyer() 0xd7929345 (libmonochrome.so -profile_destroyer.cc:121 ) ProfileDestroyer::~ProfileDestroyer() 0xd5b08e57 (libmonochrome.so -callback.h:94 ) base::Timer::RunScheduledTask() 0xd58f6457 (libmonochrome.so -callback.h:65 ) base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) 0xd58f6111 (libmonochrome.so -message_loop.cc:399 ) base::MessageLoop::RunTask(base::PendingTask*) 0xd58f68b1 (libmonochrome.so -message_loop.cc:411 ) base::MessageLoop::DoDelayedWork(base::TimeTicks*) 0xd5d8b8bb (libmonochrome.so -message_pump_android.cc:68 ) base::MessagePumpForUI::DoRunLoopOnce(_JNIEnv*, base::android::JavaParamRef<_jobject*> const&, unsigned char) 0xd090e37d (Chrome.odex + 0x0003637d ) Which seems like it might be a corrupted profile, but +profiles folks.
,
May 18 2018
,
May 18 2018
Hey dear guys. How should do to resolve this issue?
,
Jun 1 2018
--Chrome Identity automated triaging-- This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 1 2018
Moving back to Untriaged since this is an Untriaged crash.
,
Jun 12 2018
Hey,Dear guys. Is there any new updated? This issue still remain. Please help to analysis it Thanks very much.
,
Jun 12 2018
I do not see any crashes with this signature in M67 (internal link https://crash.corp.google.com/browse?q=expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27ProfileDestroyer%3A%3A~ProfileDestroyer%27#samplereports ) well.li@longcheer.corp-partner.google.com: Can you still reproduce this on a Chrome M67 or newer?
,
Jun 21 2018
well.li@longcheer.corp-partner.google.com: Ping on the question at comment #11.
,
Jul 23
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 2
,
Sep 3
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by pnangunoori@chromium.org
, Apr 24 2018Components: Internals>Media
Labels: Needs-Milestone Needs-Feedback