You could try to install the regular flash player (non debug) in chrome and disable the default bundled with it.
On 10 September 2014 09:59, Avi Kessner <akess...@gmail.com> wrote: > For my day to day browsing, I try to use the debug player in chrome, > because I find it's performance is much better. There seems to be some > restrictions with the Pepper Flash api on what resources it can access vs > NPAPI. It's worth the time to isolate if it's a flash player version > problem or a code problem on your side. > > brought to you by the letters A, V, and I > and the number 47 > > On Wed, Sep 10, 2014 at 10:50 AM, piotrz <piotrzarzyck...@gmail.com> > wrote: > > > Hi Guys, > > > > I am working on some Adobe Flex (v. 4.5.0) application (it using a lot of > > javascript also through ExternalInterface) and from some time we are > > noticing freeze of these application for 60 seconds in Google Chrome with > > default Flash Player plugin. > > > > I spend some time to optimize some logic in the application, but it > didn't > > help. > > > > I'm wondering whether this could be problem with default Chrome flash > > player. > > > > If you guys had any similar problems - some information on that would be > > precious. > > > > Piotr > > > > > > > > > > > > > > ----- > > Apache Flex Committer > > piotrzarzyck...@gmail.com > > -- > > View this message in context: > > > http://apache-flex-development.2333347.n4.nabble.com/Flash-freeze-for-60-seconds-in-Chrome-tp40638.html > > Sent from the Apache Flex Development mailing list archive at Nabble.com. > > > -- João Fernandes
