We fixed the blocking issues that doesn't allow us to open smart collection. Lets find the cause for "listener is null" +++ This bug was initially created as a clone of Bug #1034301 +++ JavaScript Error: "listener is null" {file: "jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider.js" line: 279}]

[Blocking Requested - why for this release]:

Garvan, can you take a look?

Next week I will. Requires a memory throttle, which is bizarre, I wouldn't have expected it to be memory related.

Took a quick look, planning to debug later in the week, some notes: - Repro'd on today's m-c Flame - No memory throttle needed to repro Log: I/Gecko ( 295): StaticRefPtr<nsGeolocationService> nsGeolocationService::sService; I/Gecko ( 295): Geolocation::ServiceReady() I/Gecko ( 295): Geolocation::WatchPositionReady(nsGeolocationRequest* aRequest) I/Gecko ( 295): nsGeolocationRequest::allow I/Gecko ( 295): StaticRefPtr<nsGeolocationService> nsGeolocationService::sService; I/Gecko ( 295): nsGeolocationService::StartDevice( I/Gecko ( 295): GonkGPSGeolocationProvider::Startup() I/Gecko ( 295): GonkGPSGeolocationProvider::RequestSettingValue(char* aKey) I/Gecko ( 295): GonkGPSGeolocationProvider::Init() I/Gecko ( 295): GonkGPSGeolocationProvider::GetGPSInterface() E/GeckoConsole( 295): [JavaScript Error: "this.listener is null" {file: "jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider.js" line: 517}] I/Gecko ( 295): GonkGPSGeolocationProvider::Watch(nsIGeolocationUpdate* aCallback) I/Gecko ( 295): CachedPositionAndAccuracy I/Gecko ( 295): Geolocation GeolocationService::u[date accruacy I/Gecko ( 295): Geolocation::HighAccuracyRequested() I/Gecko ( 295): Geolocation::NotifyAllowedRequest(nsGeolocationRequest* aRequest) I/Gecko ( 295): nsGeolocationRequest::SetTimeoutTimer I/Gecko ( 295): nsGeolocationRequest::StopTimeoutTimer I/Gecko ( 295): GonkGPSGeolocationProvider::Handle(const nsAString& aName,

What is the user impact of this bug?

(In reply to Jason Smith [:jsmith] from comment #5) > What is the user impact of this bug? I don't know. Maybe geolocation is not working? Garvan might know.

I see no impact on geolocation in the browser, it was working fine for me when I saw this show up in the log. Bug #1034301 masks it completely. It certainly still a bad thing, and we need to root it out and fix it.

Backlog since we don't have proof of any user impact in geolocation.

I have been back on B2G geolocation bugs for the past week, and I haven't seen this once. I tried today throttling the Flame to 256, and - repro the steps mention with loading the smart collections a second time, - run through my own geolocation tests (http://is.gd/navrag)