New issue
Advanced search Search tips

Issue 757100 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
lafo...@chromium.org
ihf@chromium.org
adobe-flash@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Win][Chrome] Flex component hangs on repeated use.

Project Member Reported by adobefla...@gmail.com, Aug 18 2017 
Fail : 27.0.0.97 + Chrome(ver:60) + Win7
Fail : 26.0.0.137 + Chrome(ver:60) + Win7
Fail : 21.0.0.242 + Chrome(ver:60) + Win7 

1. From the attached project, open testChrome.html
2. The button uses NavigateToURL api to open google.com in a new tab
3. Click the button multiple time, 30-40 time. Sometime it reproduces within 10 times

Result: After clicking the button multiple, the button component stops updating its color from dark to light grey when the mouse pointer goes on and off the button. Also, the button's functioning remains unaffected by this behaviour and it continues to open the URL.

Expected: The button component should update its color each time the mouse point hovers on and off it.

Running bisect-builds results:
You are probably looking for a change made after 464648 (known good), but no lat
er than 464656 (first known bad).
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/4dcdb6bbf30724ed511754410d
a319c35c3546ca..d525c83dc997c24ecd618d45c2d932cd2e7feccc
TestChrome.zip
2.2 MB Download

Comment 1 by adobefla...@gmail.com, Aug 18 2017 

If simply drag/dropping TestChrome.html to Chrome would not work as SecurityError would be thrown while the Flex components are getting loaded. Instead, we can make it work by placing the test files on a webserver, such as the python simple web server which we can bring up with this command line: python -m SimpleHTTPServer (be sure to run the command off the extracted dir, such as %HOMEPATH%\Downloads\TestChrome). After that, the test file can be loaded by going to http://127.0.0.1:8000/TestChrome/bin-debug/TestChrome.html.

Comment 2 by adobefla...@gmail.com, Aug 18 2017 

https://forums.adobe.com/thread/2370985 
There is a similar bug on the user's forum.

Comment 3 by adobefla...@gmail.com, Aug 18 2017

Cc: lafo...@chromium.org adobe-flash@chromium.org ihf@chromium.org

Comment 4 by lafo...@chromium.org, Aug 21 2017 

I'm having a bit of trouble narrowing this one down.

The forum thread seemed to imply that the issue described there (i.e. freezing of Flash content after bring a background tab to the foreground) was present on both Firefox and Chrome.  How confident are we that it's the same issue?

Also given the complexity of repro (i.e. relying on 30-ish clicks), would it be possible to double check the bisect?

Comment 5 by adobefla...@gmail.com, Sep 28 2017 

Re-run bisect build using user's forum https://forums.adobe.com/thread/2370985 with http://www.dhs.state.il.us/accessibility/tests/flash/video.html
You are probably looking for a change made after 464648 (known good), but no later than 464656 (first known bad).     CHANGELOG URL:                                                                                                           https://chromium.googlesource.com/chromium/src/+log/4dcdb6bbf30724ed511754410da319c35c3546ca..d525c83dc997c24ecd618d45c2d932cd2e7feccc

Comment 6 by dtapu...@chromium.org, Feb 11 2018

Components: Internals>Plugins>Flash
►

Sign in to add a comment