Closed
Bug 721905
Opened 13 years ago
Closed 2 years ago
On Bing Maps, layers have very large visible regions, causing high memory usage
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 717521
People
(Reporter: ajuma, Unassigned)
References
Details
Panning and zooming on Bing Maps on OS X, Nightly's memory usage spikes as high as 3GB. It turns out that we have Thebes layers and container layers whose visible region is being set to (what seems like) a very large area -- as large as 57524744 by 57524732.
|
||
Comment 1•13 years ago
|
||
This should be a problem on Windows, we have layer managers there that simply don't work with visible regions over 4096x4096 (in case of D3D9) or 8192x8192 (in case of D3D10).
|
||
Comment 2•13 years ago
|
||
I couldn't recreate this problem on Windows. Was there any specific combination of panning/zooming that caused the large visible regions? I'll try with Linux too at some point, although I'm having driver issues on Linux at the moment...
|
Reporter | |
Comment 3•13 years ago
|
||
(In reply to Nick Cameron from comment #2)
> I couldn't recreate this problem on Windows. Was there any specific
> combination of panning/zooming that caused the large visible regions?
On OS X, it was zooming in and out a few (< 5?) times, and then panning while zoomed in.
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•