Closed
Bug 1398599
Opened 7 years ago
Closed 7 years ago
Align StrictMode NetworkOnMainThread penalty between automation and developer builds
Categories
(Firefox for Android Graveyard :: General, enhancement)
Tracking
(firefox57 fixed)
RESOLVED
FIXED
Firefox 57
Tracking | Status | |
---|---|---|
firefox57 | --- | fixed |
People
(Reporter: JanH, Assigned: JanH)
Details
Attachments
(1 file)
Since Honeycomb, the default penalty for main thread network access is killing the process, so our way of enabling strict mode for everything in logging mode (https://dxr.mozilla.org/mozilla-central/rev/c71b01e993510268bab7d60154b2f80692fd507d/mobile/android/base/java/org/mozilla/gecko/GeckoApp.java#1897) has the unfortunate side effect of making our developer builds more forgiving than our release builds.
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jh+bugzilla
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8907259 [details] Bug 1398599 - Use default network access StrictMode policy on developer builds, too. https://reviewboard.mozilla.org/r/178932/#review184434
Attachment #8907259 -
Flags: review?(snorp) → review+
Pushed by mozilla@buttercookie.de: https://hg.mozilla.org/integration/autoland/rev/dbe68b8f1f4c Use default network access StrictMode policy on developer builds, too. r=snorp
Comment 4•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/dbe68b8f1f4c
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 57
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•