Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox (12.0, Ubuntu) freezes on Bing maps

  • 3 replies
  • 5 have this problem
  • 1 view
  • Last reply by 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)

All Replies (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?!