為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox (12.0, Ubuntu) freezes on Bing maps

  • 3 回覆
  • 5 有這個問題
  • 1 次檢視
  • 最近回覆由 philipp

more options

Hello,

When I try and use Bing maps (maps.bing.co.uk, I live in UK), firefox gets very slow and freezes after about 3 zoom or move operations. I've tried disabling hardware acceleration - with accel on, the whole X server freezes, without it just firefox. I've also tried turning network.prefetch-next off, to no avail. Safe mode does not help either.

I know there's a bug report at https://bugzilla.mozilla.org/show_bug.cgi?id=717521 but it's marked as fixed.

I recently installed chromium and it can handle Bing maps on my system with no problems.

System:

IBM thinkpad Z60m / Ubuntu 10.04 (lucid) / 2GhZ processor, 1GB RAM / Kernel 2.6.32-41-generic, Gnome 2.30.2 / Firefox 12.0 (Ubuntu)

Hello, When I try and use Bing maps (maps.bing.co.uk, I live in UK), firefox gets very slow and freezes after about 3 zoom or move operations. I've tried disabling hardware acceleration - with accel on, the whole X server freezes, without it just firefox. I've also tried turning network.prefetch-next off, to no avail. Safe mode does not help either. I know there's a bug report at https://bugzilla.mozilla.org/show_bug.cgi?id=717521 but it's marked as fixed. I recently installed chromium and it can handle Bing maps on my system with no problems. System: IBM thinkpad Z60m / Ubuntu 10.04 (lucid) / 2GhZ processor, 1GB RAM / Kernel 2.6.32-41-generic, Gnome 2.30.2 / Firefox 12.0 (Ubuntu)

所有回覆 (3)

more options

Do you normally have a slow connection?

more options

It's not super fast but it can handle skype; google maps work fine and so does Bing on chromium. Speedtest.net gives me 39ms ping, 1.96 Mb/sec download, 1.93 Mb/s upload.

more options

hello, i'm not sure if i'm reading the bugzilla entry correctly but the target milestone is set to mozilla13 (=firefox 13), so maybe it will just finally be fixed with the next update?!