Frozen playback in long recording

Bug #1462864 reported by Kenneth Wilkins
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Kazam Screencaster
New
Undecided
Unassigned

Bug Description

When I have recordings that are long (1.5+ hrs) I'm seeing playback "freeze" around 1hr 30min.

The videos time continues to move forward but the image is stuck.

Bug was seen on Mplayer and VLC

Revision history for this message
Kenneth Wilkins (kenneth-gene) wrote :

I ran ffmpeg -v error -i Screencast\ 2015-07-02\ 23:44:10.mp4 -f null - 2>errror.log

the output error.log showed a massive amount of errors; an example of which is below.

[h264 @ 0x7f8e4c4b8900] AVC: nal size 385876010
[h264 @ 0x7f8e4c4b8900] non-existing PPS 4 referenced
[h264 @ 0x7f8e4c4b8900] decode_slice_header error
[h264 @ 0x7f8e4c4b8900] FMO not supported
[h264 @ 0x7f8e4c4b8900] reference overflow (pps)
[h264 @ 0x7f8e4c4b8900] illegal POC type 32
    Last message repeated 3 times
[h264 @ 0x7f8e4c4b8900] AVC: nal size 385876010
[h264 @ 0x7f8e4c4b8900] no frame!
[h264 @ 0x7f8e4c58a8e0] AVC: nal size -201326569
    Last message repeated 1 times
[h264 @ 0x7f8e4c58a8e0] no frame!
[h264 @ 0x7f8e4c49af00] AVC: nal size -872415184
    Last message repeated 1 times
[h264 @ 0x7f8e4c49af00] no frame!
[h264 @ 0x7f8e4c4a3620] AVC: nal size 16148480
    Last message repeated 1 times
[h264 @ 0x7f8e4c4a3620] no frame!
[h264 @ 0x7f8e4c6934e0] AVC: nal size 393019392
    Last message repeated 1 times
[h264 @ 0x7f8e4c6934e0] no frame!
[h264 @ 0x7f8e4c6da720] AVC: nal size 2042822657
    Last message repeated 1 times
[h264 @ 0x7f8e4c6da720] no frame!
[h264 @ 0x7f8e4c721c60] AVC: nal size 1694499270
    Last message repeated 1 times
[h264 @ 0x7f8e4c721c60] no frame!
[h264 @ 0x7f8e4c7691a0] AVC: nal size 1804800
    Last message repeated 1 times
[h264 @ 0x7f8e4c7691a0] no frame!
[h264 @ 0x7f8e4c7b06e0] AVC: nal size -1895824707
    Last message repeated 1 times
[h264 @ 0x7f8e4c7b06e0] no frame!
Error while decoding stream #0:0: Invalid data found when processing input
    Last message repeated 1 times
[h264 @ 0x7f8e4c4b8900] AVC: nal size 660736
    Last message repeated 1 times
[h264 @ 0x7f8e4c4b8900] no frame!
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 0x7f8e4c58a8e0] AVC: nal size 524877824
    Last message repeated 1 times
[h264 @ 0x7f8e4c58a8e0] no frame!
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 0x7f8e4c49af00] AVC: nal size -1198856941

There are almost 700k lines of this from a 5.5 hr recording totaling 13.2 GB

Revision history for this message
Kenneth Wilkins (kenneth-gene) wrote :

40 min recording had no errors.
1 hour recording had no errors.

2 hour recording had errors.

Noticed these errors this time

[h264 @ 0x7f651ae4c000] decode_slice_header error
[h264 @ 0x7f651ae4c000] slice type 32 too large at 364

Revision history for this message
Krzysztof Brodacki (kbrodacki) wrote :

Hello,

I have the same issue with 2 of my screen casts.

First is like ~42 minutes long and it freezes in playback at 36:42
Second one (more important) is like 1h and it's frozen at 42:20

I don't know if it is related/relevant, however both files are quite big (see my question posted here: https://answers.launchpad.net/kazam/+question/273052)

I'm also putting ffmpeg error log, however as attachment, cause it's to big to paste it (I think most of the entries are repeatable, however not removing them - this log is for 1h movie).

Please let me know if you need this file to analyze problem, it is 6,4GB, I can give you sftp access if you wish, it's no problem.

Hope with @Kenneth we will find help with this.

Cheers

Revision history for this message
Krzysztof Brodacki (kbrodacki) wrote :

Hi Guys,

I don't know how often you read those bugs reports... Can we at least get any information that you saw this issue and you will have time to look at it / reproduce issue in some period of time: 2 weeks, month, quarter, whenever? :)

Kazam is great app, I've tried already others and I must say this one is the best...

If this bug is still open without response let's say till December, I'm going to debug and test Kazam with long screencast. I know that open projects relies on having time for them but it would be good that you guys let us know if you are going to deal with this problem or simply not, cause only me and @Kenneth reported it.

Regards,
KB

Revision history for this message
Krzysztof Brodacki (kbrodacki) wrote :
Download full text (3.6 KiB)

Hi Guys,

so posting debug results from Kazam for 1 hour 22 minutes 16 seconds screencast (playback available only for 30 first minutes):

krzysiek@k-y500:/usr/share/doc/kazam$ kazam --debug --nosound
DEBUG Kazam - Starting ...
DEBUG Kazam - Running on: Ubuntu 15.04
DEBUG Kazam - Kazam version: 1.4.5 NCC-80102
DEBUG Kazam - Starting new instance ...
DEBUG Prefs - XDG_PICTURES is a directory and accessible
DEBUG Prefs-HW - Getting hardware specs
DEBUG Prefs-HW - Getting Video sources.
DEBUG Prefs-HW - Found 1 monitor(s).
DEBUG Prefs-HW - Monitor 0 - X: 0, Y: 0, W: 1920, H: 1080
DEBUG Main - Gstreamer version detected: 1.4.5.0
DEBUG Main - Setting variables.
DEBUG Main - Connecting indicator signals.
DEBUG Main - Starting in silent mode: False
DEBUG Indicator - Indicatior silent: False
DEBUG Indicator - Trying to bind hotkeys.
DEBUG Main - Main Window UI setup.
/usr/lib/python3/dist-packages/kazam/app.py:145: Warning: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize'
  self.builder.add_from_file(os.path.join(prefs.datadir, "ui", "kazam.ui"))
DEBUG Main - Unable to get name for '<Adjustment object at 0x7f5faf5417e0 (GtkAdjustment at 0x1809b80)>'

(kazam:9854): Gtk-WARNING **: Can't set a parent on widget which has a parent

(kazam:9854): Gtk-WARNING **: Can't set a parent on widget which has a parent

DEBUG Main - Capture cursor: True.
DEBUG Main - Capture cursor_pic: True.
DEBUG Main - Capture borders_pic: True.
DEBUG Main - Record clicked, invoking Screencast.
DEBUG GStreamer - Audio_source : None
DEBUG GStreamer - Audio2_source : None
DEBUG GStreamer - Video_source: {'height': 1080, 'x': 0, 'y': 0, 'width': 1920}
DEBUG GStreamer - Xid: None
DEBUG GStreamer - Area: None
DEBUG GStreamer - Capture Cursor: True
DEBUG GStreamer - Framerate : 15.0
DEBUG GStreamer - Coordinates SX: 0 SY: 0 EX: 1919 EY: 1079
DEBUG GStreamer - testing for xid: None
DEBUG GStreamer - Codec: H264 (MP4)
DEBUG GStreamer - Filesink: /home/krzysiek/Videos/kazam_pkpqohut.movie
DEBUG GStreamer - Linking Video
DEBUG GStreamer - Link mux -> file queue: True
DEBUG GStreamer - Link file queue -> sink: True
DEBUG Main - Hiding main window.
DEBUG Main - Counter finished.
DEBUG Indicator - Recording started.
DEBUG GStreamer - Setting STATE_PLAYING
DEBUG Indicator - Recording stopped.
DEBUG Main - Stop request.
DEBUG GStreamer - Sending new EOS event
DEBUG Main - Recorded tmp file: /home/krzysiek/Videos/kazam_pkpqohut.movie
DEBUG Main - Waiting for data to flush.
DEBUG GStreamer - Received EOS, setting pipeline to NULL.
DEBUG GStreamer - Emitting flush-done.
DEBUG Main - Done Recording initialized.
DEBUG Main - Done recording signals connected.
DEBUG Done Recording - Continue - Save (2).
DEBUG Save Dialog - Save dialog called with path: None
DEBUG Save Dialog - Previous path invalid, setting it to: /home/krzysiek/Videos
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
DEBUG Main - Save Done, result: /home/krzysiek/Videos
DEBUG Main - Quit requested.
INFO Main - Unable to delete one of the temporary files. Check your temporary directory.
DEBUG Kazam - Finishing ...

This is not ...

Read more...

Revision history for this message
Tomislav (hefest) wrote :

Had what looks like the same bug cost me most of my recording this evening: everything beyond the 40' mark seem unlegible. Mplayer output:

[h264 @ 0x7f14618bb920]Invalid NAL unit size (108256 > 61237).
[h264 @ 0x7f14618bb920]Error splitting the input into NAL units.
Error while decoding frame!
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f146254d2a0]stream 0, offset 0xc8ecce90: partial file
A:2403.5 V:2403.5 A-V: 0.001 ct: 0.090 0/ 0 24% 11% 1.5% 0 0

Exiting... (End of file)

$ ffmpeg -v error -i myfile -f null - 2>/tmp/error.log

[h264 @ 0x55e612488a40] Invalid NAL unit size (108256 > 61237).
[h264 @ 0x55e612488a40] Error splitting the input into NAL units.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55e6124398c0] stream 1, offset 0xc8ee7c7e: partial file
myfile: Invalid data found when processing input
Error while decoding stream #0:0: Invalid data found when processing input
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55e6124398c0] stream 1, offset 0xc8ee7deb: partial file
myfile: Invalid data found when processing input

How is it possible that this doesn't affect more people?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.