Re: [Motion-user] [ANNOUNCE] Motion Snapshot Release 3.2.1_snap17

[Kenneth L. <ke...@la...>]

At 17:59 2005-05-16, you wrote:
>On Mon, 16 May 2005, Kenneth Lavrsen wrote:
>
> >
> >
> > Motion Snapshot Release 3.2.1_snap17
> >
> > Release Notes
> > 3.2.1 snap17 - 16 May 2005
>
>Hi,
>
>You have forgot to include my previous chdir patch =;-(

Yes. Sorry. I have edited my sources now. Will be in next snap.


>BTW I have some bugs in motion snapshot Release 3.2.1_snap17
>
>- Bug1: header_get() doesn't always in add a \0 string terminator.
>Please find a little patch to solve this problem.

I have applied your patch. Will be in next snap.

>- Bug2: Sometimes motion try to free an invalid memory area
>for (j=0; config_params[j].param_name != NULL; j++) {
>   if (config_params[j].copy == copy_string) {
>   void **val;
>   val=(void *)cnt_list[i]+config_params[j].conf_value;
>   if (*val) {
>/* FIXME BUG */
>    free(*val);
>    *val = NULL;
>   }
>  }
>}
>
>Except by removing the lines, I haven't found how to solve
>the problem.

I have been looking at this. I need to test a bit. I have some ideas. Can 
you tell me the circumstances where it happens and the exact error message?
I do not see the problem. So it can be related to how the config files are 
done. Can you post yours?



>- Bug3: Sometimes Ctrl-C doesn't kill one of thread
>Motion output with 3 netcams:
>[3] netcam: exit netcam_loop()
>...
>[1] netcam: exit netcam_loop()
>...
>[2] netcam: exit netcam_loop()
>Thread 2 exiting
>Thread 1 exiting
>Here, a thread is still waiting on a futex/mutex, so motion doesn't stop.

I guess I need to get involved in this code now. I have not yet taken the 
2-3 days to really study and understand the new netcam code.


>- "Bug" 4: Motion is eating 100% of my PIII 800 with the 3 netcam
>in 640x480 (framerate 10, low_cpu 5). When a motion is detected,
>a msmpeg4 file is created, the msmpeg4 framerate (confirmed by timelapse)
>drops to 1 per s after the motion detection!

PIII 800. One would think it should be enough but you do run a large 
framerate. The drop is because the computer is too busy making mpegs and 
writing on the disk.
Do you have a fast enough disk running DMA?
Enough RAM? Swap files will kill you.
Saving jpegs?


Kenneth


-- 
Kenneth Lavrsen,
Glostrup, Denmark
ke...@la...
Home Page - http://www.lavrsen.dk