#173 lives using 100% of cpu

lives-exe (67)

When trying to encode a video file in lives 1.6.1 on opensuse 12.1 x86_64 Desktop PC, lives fails to open the encode video dialog box and starts using 100% of the cpu. This only happens on a cpu with more than one core. Also when opening a video file from hard disk it will also use 100% of cpu and you will have to click the cancel/pulse button to get lives to finally open the video file. This also only happens on a PC with a cpu of more than one core as it does not happen in a virtual machine with one cpu core assigned to the VM. My PC specs are as follows: Intel Quad Core i7 CPU, 4GB RAM, 1GB NVIDIA Video Card, Intel DH55TC Mboard, Intel HD Sound, KDE 4.7 (latest version shipped with opensuse 12.1).


  • Salsaman

    Salsaman - 2012-03-09

    Unable to reproduce this on either a core2 duo running fedora16, or a triple core AMD running ubuntu 11.4

    Please provide more information:

    • what encoder/format/audio codec are you using to encode
    • what is the format of the video you are trying to open
  • James

    James - 2012-03-13

    When I try opening the Encode Video dialog box from the "File" Menu (the menu across the top of the screen with the option to open video files & save video files etc) Lives pulses & locks up with 100% cpu usage. I installed it via RPM software package from packman.links2linux.org I don't even get to type in a file name or even see the Encode Video dialog box before it locks up with 100% cpu usage, it also jumps from one cpu to another with the 100% cpu usage. Also when I try to open the multtrack interface it does the same thing. I've tryed uninstalling & reinstalling both Lives and opensuse 12.1 but it does not make any difference.

  • Salsaman

    Salsaman - 2012-03-13

    Just as a test, what happens if you remove all the files from /usr/lib/lives/plugins/encoders/

  • James

    James - 2012-03-15

    Now when I start Lives, I get the error message in the screen dump I took called 'lives-noencodererr.png' (attached). The "Encode Clip As..." option in the "File" menu is now also greyed out, therefore I cannot even select the "Encode Clip As..." option. On the other hand the "MULTITRACK mode" option in the "Edit" menu now seems to work, without causing Lives to hang & the 100% cpu usage. As I don't have internet at home I have to use internet on another PC which is not at home.

  • Salsaman

    Salsaman - 2012-03-15

    ok...so now you can try adding the encoder plugins back in one by one The most likely culprit is the multi_encoder, so you might want to leave that one till last.

  • James

    James - 2012-03-19

    I tryed what you said and deleted the 'encoder files' 1 by 1 from the "/usr/lib64/lives/plugins/encoders/" directory. In the following order with the following commands:

    jamespc:/usr/lib64/lives/plugins/encoders # rm pdf_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm sswf_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm encodedv_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm ffmpeg_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm mencoder_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm mjpegtools_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm qtutils_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm transcode_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm x264_encoder
    jamespc:/usr/lib64/lives/plugins/encoders # rm multi_encoder

    After I had deleted all files from the "/usr/lib64/lives/plugins/encoders/" directory (with the exception of the file "multi_encoder3"), the encode video dialog box finally came up. But it gave me an error message saying that I basically could not select
    any video codec & the drop down menu for both "Target Encoder" & "Output format" where also greyed out. I have attached both some screen dumps of this and I tryed to upload a quick ogg video that shows exectly what I mean about the 100% cpu usage & lock up.

  • Salsaman

    Salsaman - 2012-03-19

    Also the current ffmepg_encoder has been adjusted to take a "number of threads" parameter. So it will be a double test.

  • James

    James - 2012-03-20

    Im not sure I understand what you mean by "current ffmepg_encoder has been adjusted to take a "number of threads" parameter." Do you mean going into System Monitor and looking at the threads attached to the lives process?

  • Salsaman

    Salsaman - 2012-03-20

    No. I mean when you encode with it, it will prompt you for number of threads to use. If you set this to 1 then it will ignore threading.

  • James

    James - 2012-03-21

    All script files in "/usr/lib64/lives/plugins/encoders" backuped to zip file. The "encoders" folder emptied of all script files. All script files marked with [UA] are user actions that I have done. All script files added in the following order are marked with [***].


    The "Encode Clip As.." option is greyed out. "MULTITRACK mode" seems to work. ###

    jamespc:/usr/lib64/lives/plugins/encoders # ls -l

    total 20

    -rwxr-xr-x 1 root root 20239 Feb 17 02:49 multi_encoder3


    The "Encode Clip As..." is still greyed out. Lives locks up with 100% cpu usage, when clicking on the "MULTITRACK mode" option. ###

    [UA]Folder emptied of all contents, except multi_encoder3


    The "Encode Clip As.." option is still greyed out. Lives locks up with 100% cpu usage, when clicking on the "MULTITRACK mode" option. ###

    [UA]Deleted all script files from the "encoders" folder.


    The "Encode Clip As.." option is still greyed out. Lives locks up with 100% cpu usage, when clicking on the "MULTITRACK mode" option.

    It did not matter which file combo I tryed and even when I just coped the individual encoder files back to the "encoders" folder by themselves it kept doing the same thing. While I could be wrong the file "ffmpeg_encoder" maybe ok, because while I cannot remember exactly how I did it, I think the "MULTITRACK mode" did start working with the "ffmpeg_encoder" file in the "encoders" folder at some point. But I could not reproduce what I had done, no matter what I tryed. All I can say is that it is defiantly something to do with the file(s) in the "encoders" folder.

  • James

    James - 2012-03-21

    Can you plaese tell me exactly what else I should do, in clear steps.

  • Salsaman

    Salsaman - 2012-03-21

    Well, I do find this very odd, because only a couple of the encoders actively use threading (I think only ffmpeg and mjpegtools), and threading is only used during the actual encode process. So I am totally mystified by this (plus the fact that you seem to be the only person in the world to experience this). All of this leads me to believe that there is some other problem on your system and these are just symptoms of it.

  • James

    James - 2012-03-24

    Im not sure as to exactly what you mean in relation to "threading". I have done a clean install of opensuse 12.1 as well as Lives itself a number of times and still have the same problem with Lives. I will try another clean install of opensuse 12.1 & Lives but based on what I said before, I don't think it will make any difference. I have checked the other software installed on my PC and it all seems to work. With the exception of a very mirror bug in the KDE app "dolphin". You may well be right about another app causing the problem with Lives, the fact is I don't know one way or the other. I will try downloading another distro to see if it's only related to opensuse 12.1 & let you know if Lives still has a problem with my PC's hardware/OS.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks