搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Question For Firefox 4 and 5, but not 3 series, the Real Player 12.0.1.647 Live-connect plugin crashes so video not shown and reloading page as instructed fails on Vista 64-bit.

  • 1 个回答
  • 8 人有此问题
  • 9 次查看
  • 最后回复者为 cwdjr

more options

Try my page at http://www.cwdjr.net/video7/RoscoeGreetings.php . Click on the Real button. This page works for a Real video on Firefox 3 series and about 7 other current browsers. The Real player and plugins are up to date. The Vista 64-bit OS is up to date. On Firefox 4 and now 5, instead of a Real video you get a screen that says that the RealPlayer Live Connect-Enabled (32-bit plugin has crashed. The instruction to reload the page and try again does not work. There is no link to report the problem as is usual on most other problems of this sort. Turning the plugin off just removes the space reserved for the video. I have to revert to the Firefox 3 series to solve this problem. Doing clean re-installs of the most recent Real player and Firefox 4 or 5 does not help.

Try my page at http://www.cwdjr.net/video7/RoscoeGreetings.php . Click on the Real button. This page works for a Real video on Firefox 3 series and about 7 other current browsers. The Real player and plugins are up to date. The Vista 64-bit OS is up to date. On Firefox 4 and now 5, instead of a Real video you get a screen that says that the RealPlayer Live Connect-Enabled (32-bit plugin has crashed. The instruction to reload the page and try again does not work. There is no link to report the problem as is usual on most other problems of this sort. Turning the plugin off just removes the space reserved for the video. I have to revert to the Firefox 3 series to solve this problem. Doing clean re-installs of the most recent Real player and Firefox 4 or 5 does not help.

所有回复 (1)

more options

I filed a bug report at Bugzilla at https://bugzilla.mozilla.org/ . The bug number is 667399. It turns out that this bug was reported earlier in June of 2010 as 572801. Then Firefox 4 would have been in use. My report shows the same bug also is active in Firefox 5. Several confirmed the original bug and suggested why it happened. However apparently nothing was done during the Firefox 4 era. Could it be that difficult to correct the problem? Several other current browsers, even including IE9, do not have this problem. Someone needs to twist the tail of that Firefox to get it to correct the bug :-). Or perhaps Firefox 6 should be a special update just to correct unresolved bugs.