Flash crashes only in Chrome for Windows 7
Reported by
chris.ve...@thefoundry.co.uk,
Nov 14 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 Steps to reproduce the problem: What we're doing is loading about 16000 thumbnail images for displaying in a list. This crash only happens in Chrome for windows 7. We run the same SWF in Firefox for Windows 7, Chrome for Mac or Chrome for Linux without any problems. In these cases, we're running the latest versions of the browsers and Flashplayer. What is the expected behavior? What went wrong? We're thinking this could be an internal parameter setting for Chrome for Windows 7 that is different to the same parameter in Chrome for Mac and Chrome for Linux. We do all our development, testing and debugging on Mac OS X with Chrome for Mac, and so far this is our first platform specific problem. Crashed report ID: it's coming soon How much crashed? Just one tab Is it a problem with a plugin? Yes PepperFlash Did this work before? N/A Chrome version: 54.0.2840.98 Channel: stable OS Version: 7 Flash Version: Shockwave Flash 23.0 r0
,
Nov 14 2016
I'm currently waiting on the user to enable crash reporting and send me the crash ID. However, this problem only crashes the Pepper Flash player plugin, so I've instructed the user to also run chrome://ppapiflashcrash and chrome://ppapiflashhang. I'll supply those details as well.
,
Nov 17 2016
,
Nov 23 2016
Reporter@Could you please respond us as per comment#2 & provide us the crash ID for further investigation. Thank you.
,
Nov 23 2016
Attached are the crash IDs, but they don't seem to have been uploaded and I waiting on confirmation that crash reporting has been enabled.
,
Nov 30 2016
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 1 2016
These crash ID's are invalid, There should also be a server ID along with it. Can you please try and update us if any of them reported. Thanks.!
,
Dec 1 2016
Can you show me an example with the server ID?
,
Dec 1 2016
Attached a screen shot with server ID: Thanks.!
,
Dec 6 2016
Crash reporting is enabled but the customer's security levels are preventing the crash report from being sent. How do I enable only crashes report to be sent?
,
Dec 13 2016
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 19 2016
Can you please try on an updated chrome stable version and let us know if the issue still persists.
,
Jan 30 2017
Can we get an update on this. If it still repros on latest stable(56.0.2924.76) Please attach any sample test case for giving a try from our end.
,
Feb 27 2017
IS this crash ID of use:- Crash ID 866e8a9e-df93-4223-80b2-a4520d7759ff (Server ID: dff75e31c0000000)
,
Feb 28 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ranjitkan@chromium.org
, Nov 14 2016Labels: Needs-Feedback