Closed Bug 808866 Opened 13 years ago Closed 13 years ago

do not create location providers in child process

Categories

(Core :: DOM: Geolocation, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED
blocking-basecamp +
Tracking Status
firefox18 --- fixed
firefox19 --- fixed

People

(Reporter: dougt, Assigned: dougt)

References

Details

Attachments

(1 file)

Currently, we are creating geo providers in the child process. We shouldn't do that.
Attached patch patch v.1Splinter Review
Assignee: nobody → doug.turner
Attachment #678570 - Flags: review?(josh)
Attachment #678570 - Flags: feedback+
Comment on attachment 678570 [details] [diff] [review] patch v.1 Review of attachment 678570 [details] [diff] [review]: ----------------------------------------------------------------- I don't see how this can work. sGeoInitPending starts as true, and this patch early returns before any settings check occurs that can change that value. When we trigger an IPC content permission prompt, eventually we get an Allow repsonse which early returns because sGeoInitPending is still true, so we never reach StartDevice and never create the IPC geolocation update listeners.
Comment on attachment 678570 [details] [diff] [review] patch v.1 Yeah, next time I'll review the actual patch, as opposed to what my brain thinks it contains.
Attachment #678570 - Flags: review?(josh) → review+
This needs to be fixed or all geo apps will be killed on geo usage (see bug 808327)
blocking-basecamp: --- → +
Blocks: 808327
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: