Chrome crashed on device Pixel during hangout with desktop(Linux) |
|||||||
Issue descriptionChrome Version: 52.0.2734.0 / 8316.0.0 dev Device: Pixel Crash ID: b524201c00000000, aeb7690a00000000 What steps will reproduce the problem? 1. Join a two way successful hangout call between device Pixel user and desktop(Linux) user 2. Open another window and start playing a youtube video 3. From the device, select the screenshare option from the left side of the hangout window 4. A new window with the different screens shows up for the selection 5. Select the youtube window for screensharing and click 'Share'. Continue sharing for few minutes (5-10min) Expected result: The shared screen(youtube video) should be shown in desktop user screen with good video quality Actual result: Chrome crashes on device Pixel after few minutes of screensharing youtube video Note: 1. This issue is observed 2/3 attempts of hangouts on device Pixel 2. I will recheck hangouts on device Pixel with M51 older builds and update this bug accordingly
,
May 16 2016
I'm not sure we'll be able to investigate this issue because symbols appear to be missing. Thread 0 CRASHED [SIGSEGV @ 0x000001f8 ] MAGIC SIGNATURE THREAD 0x00007fed94cde5c8 (chrome + 0x027a45c8 ) 0x00007fed9481e94a (chrome + 0x022e494a ) 0x00007fed9481f418 (chrome + 0x022e5418 ) 0x00007fed93286d2b (chrome + 0x00d4cd2b ) 0x00007fed936f4313 (chrome + 0x011ba313 ) 0x00007fed97ad561a (chrome + 0x0559b61a ) 0x00007fed931b4e0c (chrome + 0x00c7ae0c ) 0x00007fed9319fd0f (chrome + 0x00c65d0f ) 0x00007fed931a09bc (chrome + 0x00c669bc ) 0x00007fed931a16be (chrome + 0x00c676be ) 0x00007fed93abe967 (chrome + 0x01584967 ) 0x00007fed93aa86e8 (chrome + 0x0156e6e8 ) 0x00007fed960e4225 (chrome + 0x03baa225 ) 0x00007fed93a6d15f (chrome + 0x0153315f ) 0x00007fed93a6d3d0 (chrome + 0x015333d0 ) 0x00007fed93a6beba (chrome + 0x01531eba ) 0x00007fed936f9ede (chrome + 0x011bfede ) 0x00007fed90b61fb5 (libc-2.19.so -libc-start.c:292 ) __libc_start_main 0x00007fed936f9d38 (chrome + 0x011bfd38 ) 0x00007ffd2d15efff 0x00007fed9253a03f (chrome + 0x0000003f ) 0x00007fed936f9d0f (chrome + 0x011bfd0f ) pucchakayala@, do you have any suggestions on how we can get this trace symbolized?
,
May 16 2016
Number 2 crasher on M52 dev. Looks like 2 different issues: - Hangouts crash - Debug symbols not uploaded. We had upload issues Thur 5/13 but it was resolved by the time this crash was reported (supposed to be).
,
May 16 2016
srcv@: please confirm if this was present in older builds.
,
May 17 2016
Adding vapier@: do you know why the debug symbols may have failed to load?
,
May 17 2016
Mike please take a look if you're the right owner for this.
,
May 17 2016
looks like symbol uploads failed again: https://uberchromegw.corp.google.com/i/chromeos/builders/link-release/builds/4457/steps/DebugSymbols/logs/stdio they can be resumed by hand as mentioned in issue 610902
,
May 17 2016
Let's keep this issue open for the Chrome crash :-)
,
May 18 2016
,
May 23 2016
gkihumba@: I am seeing similar crash on device Kip during some WebRTC tests with latest M52 52.0.2739 / 8350.0.0 dev. Please suggest if a separate bug has to be filed for this issue as crash is not observed during hangouts and do not appear similar to crbug/611585 Crash IDs: 70d5c1ea00000000 Crash stack trace: Thread 0 CRASHED [SIGSEGV @ 0xffffc9324d1d8800 ] MAGIC SIGNATURE THREAD 0x00007f76b17456f2 (chrome + 0x023236f2 ) 0x00007f76b1757a83 (chrome + 0x02335a83 ) 0x00007f76b01a7507 (chrome + 0x00d85507 ) 0x00007f76b1772a9c (chrome + 0x02350a9c ) 0x00007f76b1768a77 (chrome + 0x02346a77 ) 0x00007f76b176f0f0 (chrome + 0x0234d0f0 ) 0x00007f76b4b78306 (chrome + 0x05756306 ) 0x00007f76b4b78130 (chrome + 0x05756130 ) 0x00007f76b4b82427 (chrome + 0x05760427 ) 0x00007f76b33954b8 (chrome + 0x03f734b8 ) 0x00007f76b00cf1c8 (chrome + 0x00cad1c8 ) 0x00007f76b061ca5a (chrome + 0x011faa5a ) 0x00007f76b061dc58 (chrome + 0x011fbc58 ) 0x00007f76b00cf1c8 (chrome + 0x00cad1c8 ) 0x00007f76b00bc0f5 (chrome + 0x00c9a0f5 ) 0x00007f76b00bd2a8 (chrome + 0x00c9b2a8 ) 0x00007f76b09eb167 (chrome + 0x015c9167 ) 0x00007f76b09d4518 (chrome + 0x015b2518 ) 0x00007f76b303ad45 (chrome + 0x03c18d45 ) 0x00007f76b099791f (chrome + 0x0157591f ) 0x00007f76b0997b90 (chrome + 0x01575b90 ) 0x00007f76b099667a (chrome + 0x0157467a ) 0x00007f76b0622abe (chrome + 0x01200abe ) 0x00007f76ada49fb5 (libc-2.19.so -libc-start.c:292 ) __libc_start_main 0x00007f76b0622917 (chrome + 0x01200917 ) 0x00007ffe7d8b3fff 0x00007f76af42203f (chrome + 0x0000003f ) 0x00007f76b06228ee (chrome + 0x012008ee )
,
May 23 2016
Observed another crash during hangouts on device Kip with same M52 build (52.0.2739 / 8350.0.0 dev). Crash ID: adafa1ea00000000 Note: 1) Updating this bug with crashes observed on device Kip as crash stack trace is similar to trace mentioned in comment #2. 2) Just to be clear: Comment#11 mentions crash during apprtc calls on device Kip and Comment#12 mentions crash during hangouts on device Kip |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by srcv@chromium.org
, May 14 2016