Issue metadata
Sign in to add a comment
|
Chrome_Mac: Crash Report - base::RandBytes |
||||||||||||||||||||
Issue descriptionUnable to find the crash in Fracas, hence reported from Create new issue link. Product name: Chrome_Mac Magic Signature: base::RandBytes Current link: https://crash.corp.google.com/browse?q=product.name%3D'Chrome_Mac'%20AND%20product.version%3D'58.0.3029.81'%20AND%20custom_data.ChromeCrashProto.channel%3D''%20AND%20custom_data.ChromeCrashProto.ptype%3D'extension'%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D'base%3A%3ARandBytes'%20AND%20ReportID%3D'9466dfd640000000'&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#3 Search properties: product.name: Chrome_Mac product.version: 58.0.3029.81 custom_data.chromecrashproto.channel: custom_data.chromecrashproto.ptype: extension custom_data.chromecrashproto.magic_signature_1.name: base::RandBytes reportid: 9466dfd640000000 Metadata : Product Name: Chrome_Mac Product Version: 58.0.3029.81 Report ID: 9466dfd640000000 Report Time: Sun, 23 Apr 2017 01:53:29 GMT Uptime: 1000 ms Cumulative Uptime: 0 ms User Email: OS Name: Mac OS X OS Version: 0.0.0 CPU Architecture: amd64 CPU Info: family 6 model 70 stepping 1 Stack Trace ============================= Thread 0 CRASHED [EXC_BREAKPOINT / EXC_I386_BPT @ 0x000000010a2cba45 ] MAGIC SIGNATURE THREAD Stack Quality82%Show frame trust levels 0x000000010a2cba45 (Google Chrome Framework -rand_util_posix.cc:55 ) base::RandBytes(void*, unsigned long) 0x000000010a2cb995 (Google Chrome Framework -rand_util_posix.cc:47 ) base::RandUint64() 0x000000010e0bd594 (Google Chrome Framework -host_globals.cc:212 ) content::HostGlobals::AddModule(content::PluginModule*) 0x000000010e0effe8 (Google Chrome Framework -plugin_module.cc:512 ) content::PluginModule::PluginModule(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, base::FilePath const&, ppapi::PpapiPermissions const&) 0x000000010e0e2c39 (Google Chrome Framework -pepper_plugin_registry.cc:121 ) content::PepperPluginRegistry::Initialize() 0x000000010e0e2b80 (Google Chrome Framework -pepper_plugin_registry.cc:24 ) content::PepperPluginRegistry::GetInstance() 0x000000010e0267fe (Google Chrome Framework -renderer_main.cc:165 ) content::RendererMain(content::MainFunctionParams const&) 0x0000000109e0613f (Google Chrome Framework -content_main_runner.cc:836 ) content::ContentMainRunnerImpl::Run() 0x0000000109e05455 (Google Chrome Framework -content_main.cc:20 ) content::ContentMain(content::ContentMainParams const&) 0x000000010887081e (Google Chrome Framework -chrome_main.cc:121 ) ChromeMain 0x0000000108835da9 (Google Chrome Helper -chrome_exe_main_mac.c:85 ) main 0x00007fff8dde6234 (libdyld.dylib + 0x00005234 ) start 1) This is a regression crash seen from 56.0.2924.87 and crashes are also seen in latest stable #58.0.3029.81. 2) Currently its a top #25 extension crasher having 3 crashes from 3 unique client Ids. 3) Crashes are seen on latest M58 as below. 58.0.3029.81 75.00% 3 -- Latest Stable Crashes are seen only in M56 and M58 channels as follows: 58.0.3029.81 75.00% 3 56.0.2924.87 25.00% 1 4) Link to list of builds where crashes are seen: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Mac%27%20AND%20%20custom_data.ChromeCrashProto.channel%3D%27%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27extension%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3ARandBytes%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D 5) Possible suspect from the code search on the crashed file "rand_util_posix.cc" based on recent changes made. Review-Url: https://codereview.chromium.org/2725713002 mark@ : Could you please take a look into this if its related to your change. Note: Adding label ReleaseBlock-Stable as spikes are seen in latest stable #58.0.3029.81 only. Please feel free to remove the same if not appropriate. Thanks...!!
,
Apr 24 2017
This is unrelated to https://codereview.chromium.org/2725713002. It’s a CHECK failure probably caused file descriptor exhaustion. I’ve seen this elsewhere, and I filed bug 714614 to be the generic tracker that we can hang other bugs like this one from.
,
Apr 29 2017
Users experienced this crash on the following builds: Mac Canary 60.0.3083.0 - 0.27 CPM, 1 reports, 1 clients (signature base::RandBytes) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
May 29 2017
Users experienced this crash on the following builds: Mac Canary 61.0.3114.0 - 1.24 CPM, 2 reports, 2 clients (signature base::RandBytes) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
May 31 2017
Users experienced this crash on the following builds: Mac Beta 59.0.3071.71 - 0.04 CPM, 2 reports, 2 clients (signature base::RandBytes) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jul 7 2017
Just to update the latest behavior, Still crashes observed on latest stable. No crashes observed on latest beta and dev channels. Currently this crash is ranked as number #20 under extension process for Mac OS. Below information provides the comparison between previous and latest channels including total number of instances. +--------------------------------------------------+ |Latest Channel | Previous Channel | +--------------------------------------------------+ |59.0.3071.115 - 46 | 59.0.3071.109 - 8 |--> Stable +--------------------------------------------------+ Link to the list of the builds getting crash: --------------------------------------------- https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Mac%27%20AND%20%20custom_data.ChromeCrashProto.channel%3D%27%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27extension%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3ARandBytes%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D
,
Jul 24 2017
Just to update the latest behavior of the crash. This crash is still observed in Stable. Below are the instances. 59.0.3071.115 23.97% 151 - Stable Link to the list of the builds ============================== https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Mac%27%20AND%20%20custom_data.ChromeCrashProto.channel%3D%27%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27extension%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3ARandBytes%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D Thanks!!
,
Oct 6 2017
Users experienced this crash on the following builds: Mac Canary 63.0.3234.0 - 0.68 CPM, 1 reports, 1 clients (signature base::RandBytes) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Oct 19 2017
Users experienced this crash on the following builds: Mac Canary 64.0.3244.0 - 0.86 CPM, 1 reports, 1 clients (signature base::RandBytes) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Oct 24 2017
Users experienced this crash on the following builds: Mac Beta 62.0.3202.62 - 0.09 CPM, 4 reports, 3 clients (signature base::RandBytes) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Apr 9 2018
Issue 830181 has been merged into this issue.
,
Jul 23
Just to update the latest behavior of this issue in the latest channels: Still seeing 100 crashes from 99 clients so far on latest Stable - 67.0.3396.99 on Mac OS. This crash is ranked as number #29 in 'Extension' Stable crashes. Crashes are not observed on latest Beta, Dev and Canary builds. Link to the list of builds: ------------------------- https://crash.corp.google.com/browse?q=product_name%3D%27Chrome_Mac%27+AND+expanded_custom_data.ChromeCrashProto.ptype%3D%27extension%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3ARandBytes%27#-productname:1000,productversion:100,-magicsignature:50,-magicsignature2:50,-stablesignature:50,-magicsignaturesorted:50 Thanks!
,
Sep 11
Just seen the the same failure. The suspicious fact is that another thread is also inside RandBytes. Is that just a coincidence or could that be a reentrancy issue? https://crash.corp.google.com/browse?q=EXISTS+%28SELECT+1+FROM+UNNEST%28CrashedStackTrace.StackFrame%29+WHERE+FunctionName+like+%27%25PoissonAllocation%25%27%29&stbtiq=&reportid=cd7b82322d7cb26f&index=3#4 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mark@chromium.org
, Apr 24 2017