Closed
Bug 844399
Opened 11 years ago
Closed 11 years ago
lock fennec in landscape mode for demo purposes
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dmosedale, Unassigned)
Details
(Whiteboard: [getUserMedia][blocking-gum-])
Attachments
(1 file)
5.81 KB,
patch
|
Details | Diff | Splinter Review |
This is a temporary workaround to allow us to offer a good demo before the portrait-mode code is landed. First cut patch at landscape locking from gcp attached. It seems to cause some crashiness, so next step is to debug and see if we can fix that.
Reporter | ||
Comment 1•11 years ago
|
||
Caught a crash in a debug build with this stuff from logcat: adb| ###!!! ASSERTION: Buffer underran: 'bufferEnd >= mCurrentTime', file /Us... adb| void mozilla::AndroidBridge::HandleGeckoMessage(const nsAString_internal... adb| leaving void mozilla::AndroidBridge::HandleGeckoMessage(const nsAString_... adb| void mozilla::AndroidBridge::HandleGeckoMessage(const nsAString_internal... adb| leaving void mozilla::AndroidBridge::HandleGeckoMessage(const nsAString_... adb| WARNING: MediaPipeline Transport failed. This is not properly cleaned up... adb| WARNING: MediaPipeline Transport failed. This is not properly cleaned up... adb| WARNING: MediaPipeline Transport failed. This is not properly cleaned up... adb| WARNING: MediaPipeline Transport failed. This is not properly cleaned up... For unclear reasons, however, there are no symbols.
Reporter | ||
Comment 2•11 years ago
|
||
FWIW, the assertion seems to come from MediaStreamGraphImpl::WillUnderrun
Reporter | ||
Comment 3•11 years ago
|
||
Excitingly, it seems much more difficult to provoke the crash in debug builds. I have, however, seen plenty of instances of the Buffer underran assertion without any crashes, suggesting it's probably unrelated. I have not seen more of the MediaTransport warnings, for whatever that's worth.
Reporter | ||
Comment 4•11 years ago
|
||
I'm now finding it almost impossible to reproduce the crashiness of the landscape-only patch on my own builds. I am, however, still occasionally seeing the incoming call web content get laid out in a way where the buttons are not displayed at all, making it impossible to answer the call.
Comment 5•11 years ago
|
||
This is smelling like an (existing) race condition to me, that the landscape patch somehow makes more likely to trigger.
Comment 6•11 years ago
|
||
NOTE: that underrun assertion is bug 839650. And also note that Try builds default to ASSERTIONS crash. This can be overridden in one of the files (I think in build/). It's basically something that sets the default value of the env var that controls this, and changes the default for Try. This assertion is fairly innocuous in practice. Note that regular automatic Alder builds *shouldn't* have assert-is-crash.
Updated•11 years ago
|
Whiteboard: [getUserMedia][blocking-gum-]
Comment 7•11 years ago
|
||
I understand we are doing the demos in portrait mode, as those patches were working fine, so putting this to WONTFIX.
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
•