convert fails due to resource limits #112
Comments
|
This looks like you have not enough space available on /tmp. Either you are low on disk space or /tmp is a RAM disk with insufficient space for the temp files convert created. In current master I have already fixed setting the temp folder for convert, it will now use $HOME/.cache/peek . So if possible please try the latest git revision of Peek and see if this fixes your issue. Alternatively try setting the environment variable MAGICK_TMPDIR to a directory with enough disk space and see if this helps. |
|
I'm still getting this issue with the $HOME/.cache/peek path. |
|
Please check your disc space on $HOME |
|
Disk space should not be an issue, I have 74GB free. This is on Ubuntu 17.04 Beta. |
|
Same problem on ubuntu 17.04 stable, details: I just installed 17.04 yesterday in a clean install, but prior to that, Peek worked fine in 16.10. here's the error output with Nouveau drivers: and here's the output after switching to Nvidia drivers 375.39: |
|
I think I've found the issue or at least a workaround. On my system If I change that to |
|
Good catch, I don't have this limit set. It all comes down that convert uses a huge amount of resources when converting frames to an animated GIF with the |
|
Can you guys post the output of |
|
sure, thanks for looking into this @phw |
(This is after I edited the imagemagick config file from 1gb to 10gb) |
This explains why the 1GB disk cache is not sufficient. Maybe the solution for now is to overwrite those values when launching convert. But this needs some testing with which limits peek can get away with. |
|
with Stretch (debian9), in but it's for:
|
|
I am on Ubuntu MATE: Frequently, Peek fails to write the actual result to the file saying it is a caching issue. Short recordings normally work fine. Long ones fail all the time. |
|
I have the same issue: On small/short recordings, everything works fine, but with larger animations, it spends 2-5 seconds in "Rendering", then the file does not show up. I the same resource limits for |
|
@dustinmoorenet what was the exact workaround for you? Did you change the value |
|
yes, |
phw
changed the title
|
I have a same problem. |
|
I'm also having this issue, have changed .cache/peek to have 777 permissions, didn't seem to help. running latest version from git, compiled following debian instructions.convert -list resource
|
|
Had the same issue, I can confirm that modifying the setting to 10gb works for me too. Previously it failed silently. |
|
Indeed, I had been bitten by this and had to use other tools for longer gifs, but I do prefer using Peek. It would be useful for peek at least to watch for any failures from Nevertheless, thanks for all your hard work on peek :D 👍 |
|
Hi, I confirm, editing |
|
Same here, that's the workaround! @phw This should be mentioned in the |
|
Adding |
|
Did you add that string or modify that policy? |
|
I added it to |
|
@Jokero The disk limit is not the only resource limit. Maybe more important is the memory limit. Please run |
|
I have added explicit resource limits to the call of Would be great if somebody could test this with the current master revision. See also #125 (comment) |
|
I'm tested latest version. Problem still reproducing
|
$ convert -list resource
File Area Memory Map Disk Thread Throttle Time
--------------------------------------------------------------------------------
768 16.56GB 7.7113GiB 15.423GiB 10GiB 4 0 unlimited |
|
@Jokero with these limits that shouldn't be the problem. Maybe your's is a different issue. Can you post the output of Peek when run from the command line? |
|
It happens only when I try to record long video https://gist.github.com/Jokero/a06324c081ebd15973047e0b2b0b7b7f |
|
@Jokero This shows that the process was killed by the OS, probably took too much RAM. I gues you have no or only little swap space? Did you test the latest development version? In general for what you are doing you shouldn't be using the GIF format anyway. Even if it finishes rendering the GIF, nearly 1 minute recording of 1466x987 will easily end up in file of several hundred MBs in size. Not sure how this is useful. Change the output format to WebM or MP4 in the settings. Peek's GIF recording is really meant to capture short snippets of parts of your screen. |
|
I close this issue now as I think the 1.1.0 release manages the RAM usage well enough. It can't do magic though, ImageMagick just works as it works and the GIF format is in the end just not optimized for this kind of usage anyway. |
|
@phw Development version works the same. But I totally agree with you that gif is not suited for long videos 👍 |
|
Everybody still affected by this might want to read #125 (comment) and try the latest git revision. I made some attempts to use ffmpeg directly instead of ImageMagick and this looks promising so far. |
Hi,
I'm on Debian with version below. Imagemagick failed :( any ideas?
convert -set delay 15 peekFNNEXY-2.avi peekFNNEXY-2.gifThx,
The text was updated successfully, but these errors were encountered: