Closed
Bug 779936
Opened 12 years ago
Closed 12 years ago
Aug 2 nightly busted on Galaxy S2 & S3
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox14 unaffected, firefox15 unaffected, firefox16 unaffected, firefox17 verified)
VERIFIED
FIXED
Firefox 17
Tracking | Status | |
---|---|---|
firefox14 | --- | unaffected |
firefox15 | --- | unaffected |
firefox16 | --- | unaffected |
firefox17 | --- | verified |
People
(Reporter: vlad, Assigned: vlad)
References
Details
(Keywords: regression)
Attachments
(1 file)
3.55 KB,
patch
|
snorp
:
review+
|
Details | Diff | Splinter Review |
UI comes up, but no pages ever load -- almost as if Gecko doesn't finish coming up. If opened via a URL in an intent, content area stays black; but throbber in url bar just keeps going forever. Nothing interesting in logs.
Comment 1•12 years ago
|
||
2012-08-02 Loads on my Galaxy Nexus. Anything interesting in logcat or via debugging?
Assignee | ||
Comment 2•12 years ago
|
||
Nope, nothing. Works fine for me on Galaxy Nexus, HTC One X, and Nexus 7 (modulo the allocatedirect assertion exception).
Assignee | ||
Comment 3•12 years ago
|
||
This was broken by bug 779152 -- the compositor thread is blocked in GLController.waitForValidSurface on startup.
Blocks: 779152
Assignee | ||
Comment 4•12 years ago
|
||
So we're hitting an error from TextureView: W/TextureView( 5168): A TextureView or a subclass can only be used with hardware acceleration enabled. It seems to be disabled (by default?) on this Adreno-based S3, and we're not forcing anything via our manifest (via android:hardwareAccelerated="true" in our <application> or activity, or at the window level. Working on a patch.
QA Contact: vladimir
Assignee | ||
Comment 5•12 years ago
|
||
This adds the hardwareAccelerated flag to our manifest, and also checks to make sure that we actually are hardware accelerated before using a TextureView. snorp says this should get a qa look especially on Honeycomb devices, because of different hardwareAccelerated interactions there.
Assignee: nobody → vladimir
Attachment #648733 -
Flags: review?(snorp)
Assignee | ||
Updated•12 years ago
|
Component: General → Graphics, Panning and Zooming
QA Contact: vladimir
Updated•12 years ago
|
Attachment #648733 -
Flags: review?(snorp) → review+
Assignee | ||
Comment 6•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/af61b4b10e3a
Target Milestone: --- → Firefox 17
Updated•12 years ago
|
status-firefox14:
--- → unaffected
status-firefox15:
--- → unaffected
status-firefox16:
--- → unaffected
status-firefox17:
--- → fixed
Comment 7•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/af61b4b10e3a
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 8•12 years ago
|
||
Doh, wish I'd seen this before I cleared my profile in the hope it would fix things on my S2 :-( (Comment 7 was posted by a script) If you ever need fixes released more urgently - the sheriffs will happily retrigger Nightlies for you (and we can double land directly onto mozilla-central if needs be) if that helps for the future? :-)
Keywords: regression
Summary: Aug 2 nightly busted on Galaxy S3 → Aug 2 nightly busted on Galaxy S2 & S3
Version: unspecified → Trunk
Updated•12 years ago
|
Status: RESOLVED → VERIFIED
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
•