Closed
Bug 837051
Opened 11 years ago
Closed 11 years ago
[video]some mpeg-4 format videos play abnormal.( the image of some videos is static when playing)
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-b2g:tef+, firefox21 wontfix, firefox22 wontfix, firefox23 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)
People
(Reporter: Firefox_Mozilla, Assigned: sotaro)
References
Details
(Whiteboard: [triaged:3/1] [TD-8345] [TD-9267] [TD-11447] [TD-11450][ikura])
Attachments
(10 files, 2 obsolete files)
934.90 KB,
text/plain
|
Details | |
233.73 KB,
text/plain
|
Details | |
210.74 KB,
video/3gpp
|
Details | |
584.08 KB,
application/octet-stream
|
Details | |
5.16 KB,
patch
|
sotaro
:
review+
|
Details | Diff | Splinter Review |
5.27 KB,
patch
|
sotaro
:
review+
|
Details | Diff | Splinter Review |
300.18 KB,
text/plain
|
Details | |
42.24 KB,
text/plain
|
Details | |
15.98 KB,
text/plain
|
Details | |
74.90 KB,
text/plain
|
Details |
Steps to reproduce: 1.save some mpeg-4 format videos in TF card. 2.insert this TF card and go into videos; 3.select the mpeg-4 format video to play; Expected results: 1.the video plays normally; Actual results: 1.some mpeg-4 format videos play abnormal. the image of the video is static when playing.
Reporter | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
As I know, some Android devices does have similar issue since the hardware can not support some specific mpeg4 profile. Can you test the video can not play on the same device with Android?
Updated•11 years ago
|
Flags: needinfo?(Firefox_Mozilla)
Reporter | ||
Comment 3•11 years ago
|
||
the video which can not be played on Firefox OS can be play normal in Android OS.
Flags: needinfo?(Firefox_Mozilla)
Comment 4•11 years ago
|
||
Chiajung, can you check it's limited by the decoder we use or it's a bug? Thanks.
Flags: needinfo?(chung)
Updated•11 years ago
|
Whiteboard: [triaged:3/1]
Comment 5•11 years ago
|
||
(In reply to Al Tsai [:atsai] from comment #4) > Chiajung, can you check it's limited by the decoder we use or it's a bug? > Thanks. If I can get any video has the problem I can check it later. But I have no such video in my hand... Can you provide some?
Flags: needinfo?(chung)
Comment 6•11 years ago
|
||
Comment 7•11 years ago
|
||
Hi, all, Thanks for your help and information! I have double confirmed this case. The build: 20130218070202 (Have the same problem) The build: 20130304230203 (The issue cannot be reproduced) This case work for me with latest build and my test sample(Attached). So, close it. If the issue happens again, please reopen it. Thanks!
Reporter | ||
Updated•11 years ago
|
blocking-b2g: --- → tef?
Comment 8•11 years ago
|
||
(tef- as no build information is provided in the description and comment 7 cannot reproduce)
blocking-b2g: tef? → -
Comment 9•11 years ago
|
||
Hi, According comment#7, RESOLVED-WORKSFORME. If you think it should be reopen, please proceed. thx! David
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Comment 10•11 years ago
|
||
Hi all, In my sample, with build 20130304203846, I have played 3 different videos: A) with the video from attachment 708965 [details] and I have experienced the problem described in the description of the bug. I will try to explain current behaviour better: 1- When you play the video it is normally viewed and heard, during few seconds (5 or 6). 2- After few seconds, sound and image are frozen for 2 or 3 seconds. 3- After those 2-3 seconds, the sound is resumed, but image is not. At this point the image remains frozen unless you proceed as follows: 4- If you click in "pause", the music is paused (the image remains frozen) 5- Once you click again in "play", music is resumed and image is also resumed (and accelerated until it reaches the current reproduction point). After some seconds, behaviour becames again exactly the same as described in steps 2 and 3. B) When playing video attached in comment #7, I don't see this issue, but it is too short, so I'm cannot be sure if the issue is present also with this video C) When playing video attached in this comment, I don't see this issue. What do you think? could this be caused by a problem with the video de-coding? could be related to a RAM memory issue? Would you please mind to check behaviour of the first video in other FFOS-based device, different from ours? Bug reopened until clarification. Thx!!
Reporter | ||
Updated•11 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reporter | ||
Comment 11•11 years ago
|
||
It can see the reply of comment 10.
Updated•11 years ago
|
blocking-b2g: - → tef?
Comment 12•11 years ago
|
||
(Inder, can you please take a look at this from the decoder pov?)
Assignee: nobody → ikumar
blocking-b2g: tef? → tef+
Comment 13•11 years ago
|
||
How are things going here?
Updated•11 years ago
|
Flags: needinfo?(ikumar)
Assignee | ||
Comment 14•11 years ago
|
||
I checked a playback of attachment 708965 [details] on unagi. When I tried to seek the video, video rendering update is not smooth. Even during the payback, OMXCodec::read() took from 70ms-100ms. Even during playback, buffers of OMXCodec are always almost starved. Normally OMXCodec::read() takes less than 1ms at other videos. And when seeking, OMXCodec::read()s called before and after nsMediaOmxReader::Seek() failed with following log. It says that OMXCodec::read() took 3sec then failed. But the log says OMXCodec owned 5 output bufers at the time. It seems strange. In normal video playback, 5 buffers might be enough to output videos. > E OMXCodec: [OMX.qcom.video.decoder.mpeg4] Timed out waiting for output buffers: 0/5
Assignee | ||
Comment 15•11 years ago
|
||
Log out during seek of attachment 708965 [details]. Almost all log are added by manually.
Comment 16•11 years ago
|
||
I spoke with Inder via email and he hasn't had a chance to investigate here but is planning on doing so soon.
Comment 17•11 years ago
|
||
The issue is indeed happening due to OMXCodec running out of output buffers. I am not sure why we are running out of output buffers though. Still investigating. On Android with the same OMXCodec implementation we don't see any issues.
Flags: needinfo?(ikumar)
Assignee | ||
Comment 18•11 years ago
|
||
The patch reduces two buffers stored around nsMediaOmxReader.
Assignee | ||
Comment 19•11 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #18) > Created attachment 732969 [details] [diff] [review] > patch for b2g18 - store less buffers for video playback at nsMediaOmxReader > > The patch reduces two buffers stored around nsMediaOmxReader. By applying the patch, I confirmed that attachment 708965 [details] can be seeked as normal on unagi.
Assignee | ||
Comment 20•11 years ago
|
||
Comment on attachment 732969 [details] [diff] [review] patch for b2g18 - store less buffers for video playback at nsMediaOmxReader :doublec, can you review the patch? I confirmed the patch works on unagi. The patch reduces 2 buffers stored around nsMediaOmxReader. Reducing 1 buffer did not work. Reducing 2 buffers are necessary.
Attachment #732969 -
Flags: review?(chris.double)
Comment 21•11 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #20) > Comment on attachment 732969 [details] [diff] [review] > patch for b2g18 - store less buffers for video playback at nsMediaOmxReader > > :doublec, can you review the patch? > I confirmed the patch works on unagi. The patch reduces 2 buffers stored > around nsMediaOmxReader. Reducing 1 buffer did not work. Reducing 2 buffers > are necessary. This patch seems to do more than just change the buffer size. Was that intended?
Updated•11 years ago
|
Attachment #732969 -
Flags: review?(chris.double)
Comment 22•11 years ago
|
||
I've removed review for now until I get confirmation about the additional things in the patch from Sotaro.
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Comment 23•11 years ago
|
||
(In reply to Chris Double (:doublec) from comment #21) > (In reply to Sotaro Ikeda [:sotaro] from comment #20) > > :doublec, can you review the patch? > > I confirmed the patch works on unagi. The patch reduces 2 buffers stored > > around nsMediaOmxReader. Reducing 1 buffer did not work. Reducing 2 buffers > > are necessary. > > This patch seems to do more than just change the buffer size. Was that > intended? Yes, it was intended. Change only GetAmpleVideoFrames() to 1 is not enough to fix the problem. mLastVideoFrame is one additional buffer. By remove the mLastVideoFrame, we can remove one more buffer. Total reduced buffer count becomes 2. Then I confirmed the problem was addressed on unagi.
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Updated•11 years ago
|
Attachment #732969 -
Flags: review?(chris.double)
Comment 24•11 years ago
|
||
I could verify that the patch does fix the seek issue we were seeing. Chris/Sotaro: If there are no side effects of this change then please review and commit it as soon as we can.
Assignee | ||
Comment 25•11 years ago
|
||
(In reply to Inder from comment #24) > I could verify that the patch does fix the seek issue we were seeing. > Chris/Sotaro: If there are no side effects of this change then please review > and commit it as soon as we can. doublec, can you review the patch soon?
Comment 26•11 years ago
|
||
we need this patch immediately, pls confirm when this patch OK? Thanks
Updated•11 years ago
|
Attachment #732969 -
Flags: review?(chris.double) → review+
Comment 27•11 years ago
|
||
Does not sounds like a Gaia bug. Moving to General to reflect this.
Status: UNCONFIRMED → NEW
Component: Gaia::Video → General
Ever confirmed: true
Assignee | ||
Comment 28•11 years ago
|
||
commitable pach. Carry "chris.double: review+"
Attachment #729065 -
Attachment is obsolete: true
Attachment #732969 -
Attachment is obsolete: true
Assignee | ||
Comment 29•11 years ago
|
||
Comment on attachment 734640 [details] [diff] [review] parch v2 - store less buffers for video playback at MediaOmxReader Carry "chris.double: review+"
Attachment #734640 -
Flags: review+
Assignee | ||
Comment 30•11 years ago
|
||
commitable pach for b2g18. Carry "chris.double: review+"
Attachment #734653 -
Flags: review+
Assignee | ||
Comment 31•11 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=fef6d0a068bf
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 32•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a65e8af95d39
Keywords: checkin-needed
Comment 33•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a65e8af95d39
Status: NEW → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → B2G C4 (2jan on)
Comment 34•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/6deb867802b9 https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/f56b48e52980
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → fixed
status-firefox21:
--- → wontfix
status-firefox22:
--- → wontfix
status-firefox23:
--- → fixed
Comment 35•11 years ago
|
||
Reporter said this issue could be reproduced with latest codes. Re-open this case.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 36•11 years ago
|
||
(In reply to khu from comment #35) > Reporter said this issue could be reproduced with latest codes. Re-open this > case. Which hardware is used for it? I use only unagi.
Comment 37•11 years ago
|
||
Issue reproduces: During normal playback at the start of the video the audio appears to be only in sync with the video for a while, then it is not in sync. In addition if the User slides the bar ahead then lets go, the audio is heard, but the video is static. Tested on the following Leo environment: Leo Build ID: 20130412070204 Kernel Date: Mar 15 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/950db80b82cb Gaia: 54ab4ce3f9107d1624c18bed2a09ace6bbc6601f
Assignee | ||
Comment 38•11 years ago
|
||
(In reply to mlevin from comment #37) > Issue reproduces: > During normal playback at the start of the video the audio appears to be > only in sync with the video for a while, then it is not in sync. In addition > if the User slides the bar ahead then lets go, the audio is heard, but the > video is static. > > Tested on the following Leo environment: > so, is it leo device?
Comment 39•11 years ago
|
||
I tested on Leo as per the build ID in comment 37: "Leo Build ID: 20130412070204"
Assignee | ||
Comment 40•11 years ago
|
||
Can you confirm on a device for tef? Because it is a tef+ bug. I assume it happens because of buffer starvation on the leo device. Each device uses different number of buffer for video decoding. It is a device dependent thing.
Comment 41•11 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #40) > Can you confirm on a device for tef? Because it is a tef+ bug. I assume it > happens because of buffer starvation on the leo device. Each device uses > different number of buffer for video decoding. It is a device dependent > thing. I took the same memory card out of the Leo device and placed it into the Unagi device. Issue reproduces: The audio eventually gets out of sync with the video. In addition when I slide the bar to advance the video, the video app crashes then closes and then the home screen appears. File tested both here and in comment 37: 40 MB MP4 video
Comment 42•11 years ago
|
||
(In reply to mlevin from comment #41) > (In reply to Sotaro Ikeda [:sotaro] from comment #40) > > Can you confirm on a device for tef? Because it is a tef+ bug. I assume it > > happens because of buffer starvation on the leo device. Each device uses > > different number of buffer for video decoding. It is a device dependent > > thing. > > I took the same memory card out of the Leo device and placed it into the > Unagi device. > > Issue reproduces: The audio eventually gets out of sync with the video. In > addition when I slide the bar to advance the video, the video app crashes > then closes and then the home screen appears. > > File tested both here and in comment 37: 40 MB MP4 video Unagi build for this test: Environmental Variables: Unagi Build ID: 20130411070205 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/f671fa539473 Gaia: e7e338a765e22334b40ced41489a785941382c66
Assignee | ||
Comment 43•11 years ago
|
||
(In reply to mlevin from comment #41) > (In reply to Sotaro Ikeda [:sotaro] from comment #40) > > Can you confirm on a device for tef? Because it is a tef+ bug. I assume it > > happens because of buffer starvation on the leo device. Each device uses > > different number of buffer for video decoding. It is a device dependent > > thing. > > I took the same memory card out of the Leo device and placed it into the > Unagi device. > > Issue reproduces: The audio eventually gets out of sync with the video. In > addition when I slide the bar to advance the video, the video app crashes > then closes and then the home screen appears. > > File tested both here and in comment 37: 40 MB MP4 video Thanks for the confirmation. I never see the crash on my phone. Can you attach the crash log?
Assignee | ||
Comment 44•11 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #43) > (In reply to mlevin from comment #41) > > (In reply to Sotaro Ikeda [:sotaro] from comment #40) > > > Can you confirm on a device for tef? Because it is a tef+ bug. I assume it > > > happens because of buffer starvation on the leo device. Each device uses > > > different number of buffer for video decoding. It is a device dependent > > > thing. > > > > I took the same memory card out of the Leo device and placed it into the > > Unagi device. > > > > Issue reproduces: The audio eventually gets out of sync with the video. In > > addition when I slide the bar to advance the video, the video app crashes > > then closes and then the home screen appears. > > > > File tested both here and in comment 37: 40 MB MP4 video > > Thanks for the confirmation. I never see the crash on my phone. Can you > attach the crash log? and adb shell log when the crash happens. Thanks.
Comment 45•11 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #44) > (In reply to Sotaro Ikeda [:sotaro] from comment #43) > > (In reply to mlevin from comment #41) > > > (In reply to Sotaro Ikeda [:sotaro] from comment #40) > > > > Can you confirm on a device for tef? Because it is a tef+ bug. I assume it > > > > happens because of buffer starvation on the leo device. Each device uses > > > > different number of buffer for video decoding. It is a device dependent > > > > thing. > > > > > > I took the same memory card out of the Leo device and placed it into the > > > Unagi device. > > > > > > Issue reproduces: The audio eventually gets out of sync with the video. In > > > addition when I slide the bar to advance the video, the video app crashes > > > then closes and then the home screen appears. > > > > > > File tested both here and in comment 37: 40 MB MP4 video > > > > Thanks for the confirmation. I never see the crash on my phone. Can you > > attach the crash log? > > and adb shell log when the crash happens. Thanks. Crash Log Link: https://crash-stats.mozilla.com/report/index/fe9e4d6d-3d41-487e-a6a7-f4c452130412
Assignee | ||
Comment 46•11 years ago
|
||
Thanks for the crash log. The log does not have function information. It is not clear why it happens...
Assignee | ||
Comment 47•11 years ago
|
||
take the bug. I am actually analyzing.
Assignee: ikumar → sotaro.ikeda.g
Comment 48•11 years ago
|
||
Perhaps this attached logcat can shed some light.
Assignee | ||
Comment 49•11 years ago
|
||
(In reply to mlevin from comment #48) > Created attachment 736968 [details] > Video crash logcat > > Perhaps this attached logcat can shed some light. Thanks, did you use attachment 708965 [details] for playback?
Assignee | ||
Comment 50•11 years ago
|
||
(In reply to mlevin from comment #48) > Created attachment 736968 [details] > Video crash logcat > > Perhaps this attached logcat can shed some light. There no information why the app process crashed. From the log, there are following possibility. - file is corrupted - problem to read data from SDCARD -------------------------------------------related log. 04-12 13:57:15.772: E/MPEG4Extractor(473): Video is malformed 04-12 13:57:15.772: W/OMXCodec(473): Ignore Corrupt NAL 04-12 13:57:15.772: E/MPEG4Extractor(473): Video is malformed 04-12 13:57:15.772: W/OMXCodec(473): Ignore Corrupt NAL 04-12 13:57:15.772: E/MPEG4Extractor(473): Video is malformed 04-12 13:57:15.772: W/OMXCodec(473): Ignore Corrupt NAL 04-12 13:57:15.772: E/MPEG4Extractor(473): Video is malformed 04-12 13:57:15.772: W/OMXCodec(473): Ignore Corrupt NAL
Assignee | ||
Comment 51•11 years ago
|
||
When I playback the attachment 708965 [details], I see no "Video is malformed" log.
Comment 52•11 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #51) > When I playback the attachment 708965 [details], I see no "Video is > malformed" log. sotaro, mlevin: can we also try the "smurf video" attachment example on the Leo device as well; and see if it's reproducible? attach logs and crash reports as usual. Thanks
Updated•11 years ago
|
Whiteboard: [triaged:3/1] → [triaged:3/1] [TD-8345] [TD-9267] [TD-11447] [TD-11450]
Assignee | ||
Comment 53•11 years ago
|
||
Assignee | ||
Comment 54•11 years ago
|
||
Assignee | ||
Comment 55•11 years ago
|
||
(In reply to Tony Chung [:tchung] from comment #52) > (In reply to Sotaro Ikeda [:sotaro] from comment #51) > > When I playback the attachment 708965 [details], I see no "Video is > > malformed" log. > > sotaro, mlevin: can we also try the "smurf video" attachment example on the > Leo device as well; and see if it's reproducible? attach logs and crash > reports as usual. > > Thanks I can play "smurf video" and attachment708965 [details] normally. attachment 737397 [details], attachment 737396 [details] are logcat of each playback.
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(mlevin)
Comment 56•11 years ago
|
||
(In reply to Tony Chung [:tchung] from comment #52) > (In reply to Sotaro Ikeda [:sotaro] from comment #51) > > When I playback the attachment 708965 [details], I see no "Video is > > malformed" log. > > sotaro, mlevin: can we also try the "smurf video" attachment example on the > Leo device as well; and see if it's reproducible? attach logs and crash > reports as usual. > > Thanks sotaro, tchung: Tested on same Leo environment as before: Leo Build ID: 20130412070204 Kernel Date: Mar 15 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/950db80b82cb Gaia: 54ab4ce3f9107d1624c18bed2a09ace6bbc6601f Result: 1. No crashes for this Smurf video (filename: VID-20121226-WA0000) 2. Audio is ahead of video by a small amount, thus they are not in sync. Logcat attached titled "Leo_4_12_13". Note: logcat cannot capture everything since video cannot be played while tethered to laptop. When video ended Leo was immediately tethered to laptop and logcat was then captured.
Flags: needinfo?(mlevin)
Comment 57•11 years ago
|
||
Comment 58•11 years ago
|
||
Correction to Comment 56: Logcat titled: "Logcat of Leo test with Smurf video".
Assignee | ||
Comment 59•11 years ago
|
||
(In reply to mlevin from comment #57) > Created attachment 737544 [details] > Logcat of Leo test with Smurf video From the log, it seems that there is no problem.
Assignee | ||
Comment 60•11 years ago
|
||
(In reply to mlevin from comment #56) > (In reply to Tony Chung [:tchung] from comment #52) > > (In reply to Sotaro Ikeda [:sotaro] from comment #51) > > > When I playback the attachment 708965 [details], I see no "Video is > > > malformed" log. > > > > sotaro, mlevin: can we also try the "smurf video" attachment example on the > > Leo device as well; and see if it's reproducible? attach logs and crash > > reports as usual. > > > > Thanks > > sotaro, tchung: > > Tested on same Leo environment as before: > Leo Build ID: 20130412070204 > Kernel Date: Mar 15 > Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/950db80b82cb > Gaia: 54ab4ce3f9107d1624c18bed2a09ace6bbc6601f > > Result: > 1. No crashes for this Smurf video (filename: VID-20121226-WA0000) > 2. Audio is ahead of video by a small amount, thus they are not in sync. > [2] seems different problem from the bug. Audio output for Firefox OS v1.01 does not handle audio out latency in /gecko/media/libsydneyaudio/src/sydney_audio_gonk.cpp. It might affect to [2]. I think this bug could be closed.
Comment 61•11 years ago
|
||
closing it, if we need a follow-up bug, let's open it separately
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Summary: [OPEN_][video]some mpeg-4 format videos play abnormal.( the image of some videos is static when playing) → [video]some mpeg-4 format videos play abnormal.( the image of some videos is static when playing)
Whiteboard: [triaged:3/1] [TD-8345] [TD-9267] [TD-11447] [TD-11450] → [triaged:3/1] [TD-8345] [TD-9267] [TD-11447] [TD-11450][ikura]
Comment 62•11 years ago
|
||
leo device still has a problem after adapting attached patch. Do I need to create another issue? or any one can follow up here?
Comment 63•11 years ago
|
||
Sorry for confusing.. It seems like fixed in leo device, also.
Assignee | ||
Comment 64•11 years ago
|
||
FYI, attachment 735058 [details] in Bug 832653 could provide two more buffers to gecko. I am thinking to apply it after v1.1.
Comment 66•11 years ago
|
||
When the video application retrieves thumbnail from the contents, same problem occur. (At the time video application seek to total duration /4 position) Thumbnail is show up becuase first 2~3 frames are rendered. But it delays 3 seconds for every MPEG4 encoded files to be retrieved thumbnail.
Comment 67•11 years ago
|
||
I want to reopen this issue because I think comment 66 is related to this issue. If it's not, please close the issue then I will create another one.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 68•11 years ago
|
||
(In reply to leo.bugzilla.gecko from comment #67) > I want to reopen this issue because I think comment 66 is related to this > issue. > If it's not, please close the issue then I will create another one. Please open another issue.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 69•11 years ago
|
||
(In reply to leo.bugzilla.gecko from comment #67) > I want to reopen this issue because I think comment 66 is related to this > issue. > If it's not, please close the issue then I will create another one. This bug is not related to comment 66. It is a different problem.
Assignee | ||
Comment 70•11 years ago
|
||
GetAmpleVideoFrames() of 1 in attachment 734653 [details] [diff] [review] regressed video playback especially in Bug 863441. GetAmpleVideoFrames() needs to be more than 3. Just increase the number regress this problem. Instead Bug 864230 will fix the problem caused by increase of GetAmpleVideoFrames().
You need to log in
before you can comment on or make changes to this bug.
Description
•