Chrome Version: 57.0.2987.115
Chrome OS Version: 9202.54.0
Chrome OS Platform: elm
Steps To Reproduce (presumably):
(1) Join WebX meeting?
(2) wait 4-5 minutes
(3)
Expected Result:
No tab crash.
Actual Result:
WebX meeting tab crashes
How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Every 4-5 minutes.
What is the impact to the user, and is there a workaround? If so, what is
it?
Makes using WebX meetings a painful experience.
Please provide any additional information below. Attach a screen shot or
log if possible.
From:
https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=55462083541
Feedback report shows the "every 4-5 minute" crash pattern:
2017-03-21 16:18:20.162 6 kernel : [ 588.713073] DedicatedWorker[7031]: undefined instruction: pc=00000000b8e28c8e
2017-03-21 16:18:20.163 6 kernel : [ 588.713096] Code: 0008f107 f8406819 60792d08 f873f4ed (2486deff)
2017-03-21 16:18:20.389 4 crash_reporter[7325]: [user] Received crash notification for chrome[6870] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-03-21 16:18:20.390 4 crash_reporter[7325]: [ARC] Received crash notification for chrome[6870] sig 4, user 1000 (ignoring - crash origin is not ARC)
2017-03-21 16:23:52.670 6 kernel : [ 921.219249] DedicatedWorker[7401]: undefined instruction: pc=00000000b8e28cb6
2017-03-21 16:23:52.670 6 kernel : [ 921.219260] Code: 0008f107 f8406819 60792d08 f85ff4ed (245edeff)
2017-03-21 16:23:52.794 4 crash_reporter[7867]: [user] Received crash notification for chrome[7344] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-03-21 16:23:52.794 4 crash_reporter[7867]: [ARC] Received crash notification for chrome[7344] sig 4, user 1000 (ignoring - crash origin is not ARC)
2017-03-21 16:27:35.959 6 kernel : [ 1144.499494] DedicatedWorker[8019]: undefined instruction: pc=00000000b8e28cb6
2017-03-21 16:27:35.959 6 kernel : [ 1144.499505] Code: 0008f107 f8406819 60792d08 f85ff4ed (245edeff)
2017-03-21 16:27:36.048 4 crash_reporter[8194]: [user] Received crash notification for chrome[7961] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-03-21 16:27:36.049 4 crash_reporter[8194]: [ARC] Received crash notification for chrome[7961] sig 4, user 1000 (ignoring - crash origin is not ARC)
2017-03-21 16:30:55.162 6 kernel : [ 1343.711881] DedicatedWorker[8249]: undefined instruction: pc=00000000b8e28cb6
2017-03-21 16:30:55.163 6 kernel : [ 1343.712022] Code: 0008f107 f8406819 60792d08 f85ff4ed (245edeff)
2017-03-21 16:30:55.379 4 crash_reporter[8491]: [user] Received crash notification for chrome[7327] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-03-21 16:30:55.380 4 crash_reporter[8491]: [ARC] Received crash notification for chrome[7327] sig 4, user 1000 (ignoring - crash origin is not ARC)
2017-03-21 16:34:08.714 6 kernel : [ 1537.264222] DedicatedWorker[8524]: undefined instruction: pc=00000000b8e28cb6
2017-03-21 16:34:08.715 6 kernel : [ 1537.264252] Code: 0008f107 f8406819 60792d08 f85ff4ed (245edeff)
2017-03-21 16:34:08.749 4 crash_reporter[8681]: [user] Received crash notification for chrome[8495] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-03-21 16:34:08.749 4 crash_reporter[8681]: [ARC] Received crash notification for chrome[8495] sig 4, user 1000 (ignoring - crash origin is not ARC)
2017-03-21 16:34:23.557 I bugreportd: Received request for bugreport.
This feedback report has no Client ID making it hard to find in the crash server.
However, I only see one Elm device with > 4 Chrome crashes on 57.0.2987.115, so the above probably correspond to these 5 SIGILL crashes:
1 1d71565480000000 03/21/17 21:07:45 GMT extension beta abort
2 0d80781160000000 03/21/17 20:22:34 GMT extension beta abort
3 677316c0a0000000 03/21/17 20:09:43 GMT extension beta abort
4 63e477e160000000 03/21/17 19:54:42 GMT extension beta abort
5 2157c9a160000000 03/21/17 13:28:12 GMT renderer beta abort
However, Chrome 57.0.2987.115 has no symbols on the crash server, making it even harder to identify what is crashing :(
Here is the (1) from the list above:
https://crash.corp.google.com/browse?q=reportid=1d71565480000000
Report ID 1d71565480000000
Product, version Chrome_ChromeOS, 57.0.2987.115
Process type extension
Magic Signature abort
Stable Signature abort-b93b09db
Report Time Tue, 21 Mar 2017 21:07:45 GMT
Uptime 1666 ms
Client ID 347428927e6a4ca29fe9b12c7fbf4d1f
Device Model elm-signed-mpkeys
Thread 7 CRASHED [SIGILL @ 0xeb8aecee ] MAGIC SIGNATURE THREAD
0xeb8aecee (libc-2.23.so -abort.c:124 ) abort
0xaccf5cf5 (chrome + 0x01929cf5 )
0xacd02729 (chrome + 0x01936729 )
0xafa399a6 (chrome + 0x0466d9a6 )
0xabb7a24a (chrome + 0x007ae24a )
0xeba8deed (libstdc++.so.6.0.20 -new_allocator.h:104 ) std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&)
0xeba8df41 (libstdc++.so.6.0.20 -basic_string.tcc:479 ) std::string::_M_mutate(unsigned int, unsigned int, unsigned int)
0x00000004
0xabb7a24a (chrome + 0x007ae24a )
0xab9bfb93 (chrome + 0x005f3b93 )
0xac2da3cb (chrome + 0x00f0e3cb )
0xacd0c0fe (chrome + 0x019400fe )
0xad085a23 (chrome + 0x01cb9a23 )
0xae3c3429 (chrome + 0x02ff7429 )
0xafa399a6 (chrome + 0x0466d9a6 )
0xabb6e903 (chrome + 0x007a2903 )
0xab85ab05 (chrome + 0x0048eb05 )
0xab9e7701 (chrome + 0x0061b701 )
0xad085a23 (chrome + 0x01cb9a23 )
0xeba69995 (libstdc++.so.6.0.20 -streambuf:451 ) std::ostreambuf_iterator<char, std::char_traits<char> > std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::_M_insert_int<long>(std::ostreambuf_iterator<char, std::char_traits<char> >, std::ios_base&, char, long) const
0xafa399a6 (chrome + 0x0466d9a6 )
0xab85ab05 (chrome + 0x0048eb05 )
0xabb7af72 (chrome + 0x007aef72 )
0xafa399a6 (chrome + 0x0466d9a6 )
0xabb6e903 (chrome + 0x007a2903 )
0xab85ab05 (chrome + 0x0048eb05 )
0xeba69d7b (libstdc++.so.6.0.20 -streambuf:451 ) std::ostreambuf_iterator<char, std::char_traits<char> > std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::_M_insert_int<unsigned long>(std::ostreambuf_iterator<char, std::char_traits<char> >, std::ios_base&, char, unsigned long) const
0xeba8deed (libstdc++.so.6.0.20 -new_allocator.h:104 ) std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&)
0xeba74525 (libstdc++.so.6.0.20 -basic_string.tcc:138 ) char* std::string::_S_construct<char*>(char*, char*, std::allocator<char> const&, std::forward_iterator_tag)
0xb1302306
0xeba69e99 (libstdc++.so.6.0.20 -locale_facets.h:2480 ) std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::do_put(std::ostreambuf_iterator<char, std::char_traits<char> >, std::ios_base&, char, unsigned long) const
0xeba71e9b (libstdc++.so.6.0.20 -locale_facets.h:2341 ) std::ostream& std::ostream::_M_insert<unsigned long>(unsigned long)
0xacd1694d (chrome + 0x0194a94d )
Comment 1 by sheriffbot@chromium.org
, Mar 22 2018