Huge use of processor/ webm incorrectly recording

Bug #1127432 reported by mark
14
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Kazam Screencaster
Confirmed
Undecided
David Klasinc

Bug Description

while i was making a test recording using kazam 1.3.1 i noticed that it was using 143+ of my processor which is more than any other application (with the exception of video editing software) has ever used.

also because i loved to use the Webm format in previous versions i decided i would use that and it messes with the video drastically showing only a vertical line, the debug info is:

unknown@unknown ~ $ kazam --debug
DEBUG Kazam - Starting ...
DEBUG Kazam - Running on: LinuxMint 14
DEBUG Kazam - Kazam version: 1.3.101-0ubuntu2 NX-01
DEBUG Kazam - Starting new instance ...
DEBUG Constants - Getting hardware specs
DEBUG Constants - Getting Video sources.
DEBUG Constants - Found 1 monitor(s).
DEBUG Constants - Monitor 0 - X: 0, Y: 0, W: 1920, H: 1080
DEBUG Main - Gstreamer version detected: 1.0.4.0
DEBUG Main - Setting variables.

(kazam:3874): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:239:15: Theming engine 'adwaita' not found

(kazam:3874): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:671:16: Theming engine 'adwaita' not found

(kazam:3874): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:938:16: Theming engine 'adwaita' not found
DEBUG PulseAudio - Starting mainloop.
DEBUG PulseAudio - Getting API.
DEBUG PulseAudio - Setting context.
DEBUG PulseAudio - Set state callback.
DEBUG PulseAudio - Connecting to server.
DEBUG PulseAudio - Start mainloop.
DEBUG PulseAudio - State connected.
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.
DEBUG Main - Unable to get name for '<Adjustment object at 0x1d314b0 (GtkAdjustment at 0x2054de0)>'

(kazam:3874): Gtk-WARNING **: Theme directory of theme Azenis Icons has no size field

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

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

DEBUG Prefs - Getting Audio sources.
DEBUG PulseAudio - get_audio_sources() called.
DEBUG PulseAudio - pa_sourcelist_cb()
DEBUG PulseAudio - IDX: 0
DEBUG PulseAudio - Name: b'alsa_output.pci-0000_01_00.1.hdmi-stereo.monitor'
DEBUG PulseAudio - Desc: b'Monitor of Cedar HDMI Audio [Radeon HD 5400/6300 Series] Digital Stereo (HDMI)'
DEBUG PulseAudio - pa_sourcelist_cb()
DEBUG PulseAudio - IDX: 1
DEBUG PulseAudio - Name: b'alsa_output.pci-0000_00_1b.0.analog-stereo.monitor'
DEBUG PulseAudio - Desc: b'Monitor of Built-in Audio Analog Stereo'
DEBUG PulseAudio - pa_sourcelist_cb()
DEBUG PulseAudio - IDX: 2
DEBUG PulseAudio - Name: b'alsa_input.pci-0000_00_1b.0.analog-stereo'
DEBUG PulseAudio - Desc: b'Built-in Audio Analog Stereo'
DEBUG PulseAudio - pa_sourcelist_cb() -- finished
DEBUG Prefs - Device found:
DEBUG Prefs - - 0
DEBUG Prefs - - alsa_output.pci-0000_01_00.1.hdmi-stereo.monitor
DEBUG Prefs - - Monitor of Cedar HDMI Audio [Radeon HD 5400/6300 Series] Digital Stereo (HDMI)
DEBUG Prefs - Device found:
DEBUG Prefs - - 1
DEBUG Prefs - - alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
DEBUG Prefs - - Monitor of Built-in Audio Analog Stereo
DEBUG Prefs - Device found:
DEBUG Prefs - - 2
DEBUG Prefs - - alsa_input.pci-0000_00_1b.0.analog-stereo
DEBUG Prefs - - Built-in Audio Analog Stereo
DEBUG Main - Capture cursor: True.
DEBUG Main - Capture speakers: True.
DEBUG Main - Capture cursor_pic: True.
DEBUG Main - Capture borders_pic: True.
DEBUG Main - Record clicked, invoking Screencast.
DEBUG GStreamer - audio_source : alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
DEBUG GStreamer - audio2_source : None
DEBUG GStreamer - video_source: {'y': 0, 'x': 0, 'height': 1080, 'width': 1920}
DEBUG GStreamer - xid: None
DEBUG GStreamer - area: None
DEBUG GStreamer - Capture Cursor: True
DEBUG GStreamer - Framerate : 15.0
DEBUG GStreamer - Codec: vp8enc
DEBUG GStreamer - Coordinates SX: 0 SY: 0 EX: 1919 EY: 1079
DEBUG GStreamer - testing for xid: None
DEBUG GStreamer - Codec: VP8 / WEBM
DEBUG GStreamer - Setup audio elements.
DEBUG GStreamer - Audio1 Source:
  alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
DEBUG GStreamer - Filesink: /home/unknown/Videos/kazam_hvvdcv.movie
DEBUG GStreamer - Linking Video
DEBUG GStreamer - Linking Audio
DEBUG GStreamer - Link audiosrc -> aud_in_queue: True
DEBUG GStreamer - Link aud_in_queue -> aud_caps_filter: True
DEBUG GStreamer - Link aud_caps_filter -> audioconv: True
DEBUG GStreamer - Link audioconv -> audioenc: True
DEBUG GStreamer - Link audioenc -> aud_out_queue: True
DEBUG GStreamer - Link aud_out_queue -> mux: True
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/unknown/Videos/kazam_hvvdcv.movie
DEBUG Main - Waiting for data to flush.
DEBUG GStreamer - Received EOS, setting pipeline to NULL.
DEBUG GStreamer - Emitting flush-done.
DEBUG Main - Autosaving enabled.

Revision history for this message
mark (highamma) wrote :

also should mention that the mp4 format video/audio works however still uses way to much of my resources

Revision history for this message
David Klasinc (bigwhale) wrote :

There are problems with VP8/WEBM and GStreamer leaking insane amounts of memory. I'm already talking about this with GStreamer developers. H264 should be much better in this regard.

Can you please specify more precisely what is 'way too much resources'? Too much memory is consumed? Too much CPU? You need a lot of CPU power when recording 1920x1080 video at 15 frames per second and encoding it on the fly to H264 (or VP8). Kazam will now use all but one of your CPU cores.

David Klasinc (bigwhale)
Changed in kazam:
status: New → Confirmed
assignee: nobody → David Klasinc (bigwhale)
Revision history for this message
juan (pastasjuan) wrote :

I recorded a long video for testing, and I was seeing the swap being filled while the RAM was free. Is this the same issue? Will this be fixed?

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

@juan
Isn't Kazam screen recorder that manage swap/ram, that's a kernel issue so please open a new bug report typing in a terminal ubuntu-bug linux

Best regards

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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