Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.
Flash plug-in wont load after upgrade to 40.0.2
Firefox recently auto-upgraded from 39.0.3 to 40.0.2 on two of my Win7 machines. After the upgrade neither machine could load a radio station's Flash stream. Reinstalling 39.0.3 returns the streaming to normal.
The Flash stream is called from the radio station's home page using this URL: http://player.streamtheworld.com/liveplayer.php?callsign=KTWSFM The home page is: www.thetwins.com
The call opens a new FF window and the stream starts to load but stalls on a gray screen. There are no error messages.
I tried updating both the Shockwave Flash and Adobe Flash play plug-ins to the latest version but this did not fix the stream problem.
FWIW I have not tested with other Flash web content.
It would be great if this could be fixed.
Все ответы (4)
- see if there are updates for your graphics drive drivers
- disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)
- disable hardware acceleration in the Flash plugin
https://forums.adobe.com/thread/891337 See also:
Tried your suggestions. Results are...
Display Driver: No display driver update available. Flash Protected Mode: Disabling had no effect on problem. Flash Hardware Acceleration: Disabling had no effect on problem. Flash Troubleshooting Link: Offered no solution.
I did discover that other web Flash content including 'speedtest.net' and Adobe's Flash test content played without problems.
Again, stepping back to FF v39.0.3 returns everything to normal.
Technician from TridentDigital (publisher of stream player for my radio station) spent over an hour poking around in my laptop trying to figure this out. She confirmed that IE would load Flash stream audio & video content properly but FF 40.0.3 wouldn't and appeared to stall on the video portion.
She went away scratching her head but thought she had some ideas as to what was going on after using FF's debugger and logger to gather data. She said she would get back to me.
You can try to set dom.ipc.plugins.asyncInit to false about:config page.
You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.