You found a bug! We've classified it as
EXTJS-8418
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
-
Ext JS Premium Member
IE9 navigator.geolocation memory leak (standards mode)
REQUIRED INFORMATION
Ext version tested:
Browser versions tested against:
- IE9 (9.0.8112.16421, update versions: 9.0.12)
DOCTYPE tested against:
- html
- no doctype with X-UA-Compatible "IE=edge" meta
Description:
- IE9 has a memory leak issue in GeoLocation API
- This is triggered by ExtJS initialization, so simply including ExtJS in a page is enough for IE to start leaking memory
Steps to reproduce the problem:
- hit F5 multiple times
- monitor iexplore.exe process memory consumption
The result that was expected:
- iexplore.exe process memory stays approximately the same with every refresh
The result that occurs instead:
- iexplore.exe memory consumption grows continuously
Test Case:
Code:
<!DOCTYPE html>
<html>
<head>
<script src="ext-all-debug.js"></script>
</head>
<body>
</body>
</html>
HELPFUL INFORMATION
Useful links:
Memory leak source:
- Ext.supports.init tests -> 'GeoLocation':
Code:
{
identity: 'GeoLocation',
fn: function() {
return (typeof navigator != 'undefined' && typeof navigator.geolocation != 'undefined') || (typeof google != 'undefined' && typeof google.gears != 'undefined');
}
},
Possible fix:
Code:
{
identity: 'GeoLocation',
fn: function() {
return (typeof navigator != 'undefined' && 'geolocation' in navigator) || (typeof google != 'undefined' && typeof google.gears != 'undefined');
}
},
Additional CSS used:
Operating System:
TL;DR:
This seems critical
-
Thanks for the report! I have opened a bug in our bug tracker.
Reply With Quote
