Motion - Bug Report 2005x 03x 03x 141014

BUG: /tmp is growing

/tmp is growing since the use of tmpfile.

Test case

using motion with some netcam (axis) with threads.


Motion version: 3.1.19-snap4
ffmpeg version:  
Shared libraries:  
Server OS: linux debian sarge

-- XavierNicollet - 03 Mar 2005

Follow up

idem for 3.2.1 (latest snapshot)

Perhaps a few more words describing the problem would enables us to actually do anything about it.

-- KennethLavrsen - 03 Mar 2005

Ok, it seems that it had something to do with the mjpeg support. We droped it and it works ok know. Sorry for the inconvenience.

If there is an issue with a /temp directory that grows I would very much like to know because that could be a fatal stability issue.

Can you describe the exact condition where it happens and how the temp directory grows?
  • How fast?
  • How many files?
  • What are the file names?

-- KennethLavrsen - 04 Mar 2005

The partition was 420 MB. It became full in less than a day. The files were not visible when doing some ls /tmp. It was hidden files produced by some tmpfile() call. After some lsof, it seems that the temporary files where flushed regularly. However, one of them was growing.

So in one of my threads: this work: netcam_url

This does not: netcam_url

Could I kindly ask you to attach your motion.conf and any thread config files to this topic?

-- KennethLavrsen - 07 Mar 2005

If you are capturing mjpeg video with an Axis camera, could you please try:


and see if that works? Apparently, without showlength=1 the Axis camera does not output Content-Length's in the stream. With this option, the netcam code is much more stable.

-- ChristopherPrice - 19 Mar 2005

After some more thought, I believe this bug may be related to an earlier version of motion. This would be related to the original netcam using the curl libraries. Originally, the netcam driver created temp files to process the incoming data. There must have been an issue with unlinking the temp file or something.

Also, it was only recently that Debian testing moved to motion-3.1.19. Debian stable still only has motion-3.1.16 and will remain that way.

-- ChristopherPrice - 31 Mar 2005

Yes. He probably had the old version installed with apt in /usr/bin and the newer built from sources in /usr/local/bin and in reality run the old version without knowing. I have written to Xavier directly but he does not reply.

A bug report which we cannot reproduce and the reporter does not want to follow up on can only go one way: Rejection.

If anyone else wants to add to it and put it alive again - they can do so.

-- KennethLavrsen - 31 Mar 2005

Fix record

Rejected. Lack of feedback from reporter and cannot be reproduced by developers.

-- KennethLavrsen - 31 Mar 2005
Topic revision: r10 - 31 Mar 2005, KennethLavrsen
Copyright © 1999-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.