Closed
Bug 808866
Opened 13 years ago
Closed 13 years ago
do not create location providers in child process
Categories
(Core :: DOM: Geolocation, defect)
Tracking
()
RESOLVED
FIXED
| blocking-basecamp | + |
People
(Reporter: dougt, Assigned: dougt)
References
Details
Attachments
(1 file)
|
1.12 KB,
patch
|
jdm
:
review+
baku
:
feedback+
|
Details | Diff | Splinter Review |
Currently, we are creating geo providers in the child process. We shouldn't do that.
| Assignee | ||
Comment 1•13 years ago
|
||
Assignee: nobody → doug.turner
Attachment #678570 -
Flags: review?(josh)
Updated•13 years ago
|
Attachment #678570 -
Flags: feedback+
Comment 2•13 years ago
|
||
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 3•13 years ago
|
||
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+
| Assignee | ||
Comment 4•13 years ago
|
||
This needs to be fixed or all geo apps will be killed on geo usage (see bug 808327)
blocking-basecamp: --- → +
| Assignee | ||
Comment 5•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/dbeaa765933e
https://hg.mozilla.org/releases/mozilla-aurora/rev/929f506750e1
status-firefox18:
--- → fixed
status-firefox19:
--- → fixed
| Assignee | ||
Updated•13 years ago
|
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.
Description
•