Deadlock(?) during image rendering for a jQuery gallery
Reported by
chrisrw...@gmail.com,
Oct 19 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36 Steps to reproduce the problem: 1. Have a page that dynamically creates and deletes <img> and <video> tags. 2. Leave it running for a few hundred (or thousand?) images. (I am yet to reproduce this in a simpler web page, but can consistently reproduce it on the internal app in a few minutes. The page really doesn't do much else; just uses jQuery to fetch lists of images, then cycle through them, showing them at different scales.) What is the expected behavior? No tab hang, or a tab crash in response to the tab hang. What went wrong? The renderer stops responding half way through an image load. The page refuses to close. Page Unresponsive dialogs start appearing. Pressing "kill" does not provide a crash id. A gdb backtrace from the following command is attached. $ chromium-browser --no-sandbox --renderer-cmd-prefix='xterm -title renderer -e gdb --args' The thread dump shows: * 574 threads trying to get a lock in libffmpeg.so. * 587 threads trying to get a lock in base::MessagePumpDefault::Run -> WaitableEvent::Wait * 5 threads trying to get a lock in content::CategorizedWorkerPool::Run ... and a few other threads. Tested with Ubuntu 16.10's chromium-browser 53.0.2785.143-0ubuntu1.1307, and Google Chrome Version 54.0.2840.59 (64-bit), and various previous versions. Should I have symbols for libffmpeg.so somewhere? Could someone give me a hint as to what the page is doing wrong, so I can try and reproduce it? Maybe latency on the images? Cross-origin? Did this work before? N/A Chrome version: 54.0.2840.59 Channel: stable OS Version: Ubuntu 16.10 Flash Version: Shockwave Flash 23.0 r0 I tried to report this as a crash, but the bug report wizard doesn't let you submit a report off the back of that, it just errors. I raised a separate monorail issue for this.
,
Oct 19 2016
On Win10, it just runs out of memory (before it manages to crash?). The crashes won't upload. Too big? I tried multiple times. Crash ID f7e39fd9-b1b9-4703-897e-6168a649d311 Crash report captured on Wednesday, 19 October 2016 at 22:57:49 was not uploaded Crash ID bca19f11-39d5-4b8b-a390-95ac888c80c3 Crash report captured on Wednesday, 19 October 2016 at 22:57:47 was not uploaded Crash ID 8d7e6c0a-107e-429b-9ea2-7ac048baf08c Crash report captured on Wednesday, 19 October 2016 at 22:57:23 (upload requested by user, not yet uploaded)
,
Apr 8 2017
This has started crashing on Linux, sometimes! Crash ID: crash/207aa39640000000
,
Apr 10 2017
Crash ID: crash/0a55070790000000 Yay!
,
Apr 12 2017
After a bit more poking around in a debugger, I made an even simpler reproducer: https://chrome-imglock.goeswhere.com/two.html All this does is create and delete the same video tag over and over again. The process lasts about 3 seconds on Linux, and about a minute (with multiple GPU thread crashes) on Windows. Still pretty sure the Windows case is a memory leak, not a thread/deadlock leak. Can't reproduce on Mac, another good sign that it's a specific issue.
,
Nov 7 2017
Unable to reproduce the issue on Ubuntu 14.04 using latest chrome Stable #62.0.3202.89 & on latest #64.0.3261.0. Followed below steps: 1)Opened https://chrome-imglock.goeswhere.com/ as per comment #1 -> Pressed the left and right arrow keys (and tried by holding key). 2)Observed No crash or Chrome is working fine. And also tried on opening 'https://chrome-imglock.goeswhere.com/two.html' as per comment # 5. No stack trace is seen for the mentioned Crash Ids(As per comment #3 and Comment #4) chrisrwest@ Could you please confirm are you able to reproduce this issue consistently?Please recheck this issue by creating a new profile under chrome://settings with no apps or extensions by upgrading to latest Stable #62.0.3202.89 and attach Crash Id from chrome://crashes Thanks..!!
,
May 23 2018
Closing issue as Wontfix due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. Thanks..! |
|||
►
Sign in to add a comment |
|||
Comment 1 by chrisrw...@gmail.com
, Oct 19 2016