Closed
Bug 1072148
Opened 11 years ago
Closed 11 years ago
Trying to output to a display at 1080p resolution causes b2g to crash
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cjones, Unassigned)
References
Details
I didn't spend much time diagnosing this because there are worse bugs at lower resolutions. I landed a temporary workaround that restricts resolution to 480p. This very strongly suggets memory corruption.
It's not worth looking more at this until bug 1072145 is understood.
Comment 1•11 years ago
|
||
omx video codec size limitation is expected to use the following system properties.
- ro.moz.omx.hw.max_width
- ro.moz.omx.hw.max_height
The following is hamachi's example.
https://github.com/mozilla-b2g/android-device-hamachi/blob/master/full_hamachi.mk#L19
| Reporter | ||
Comment 2•11 years ago
|
||
Hi Sotaro.
Sorry, what I meant was that if the b2g *screen* itself is 1920x1080, then b2g on the Raspberry Pi crashes. Not just for videos, but for any content like the homescreen. This is a bug in the GL stack.
Hardware video decoding and camera on the RPi is another, interesting problem :).
Summary: Trying to render at 1080p resolution causes b2g to crash → Trying to output to a display at 1080p resolution causes b2g to crash
| Reporter | ||
Comment 3•11 years ago
|
||
I'm just going to close this out for now. The crash may have been related to the buggy gfx stack, but as things stand now with SW compositing, it's just not feasible to use 1080p. So we'll revisit this in the future.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•