BUG: Motion dead after some changes of width and height parameters

floating point error

Motion is dead after some changes of width and height parameters by my PHP application.

Now server can't restart, there is a floating point error

What happened? What can I do to make it work again? I restarted my PC, but never changed.

Thank you very much

root@omnisview:~# motion -s
[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Processing config file /etc/motion/thread7.conf
[0] Motion running in setup mode.
[0] Webcam port 8087
[0] Thread device: /dev/video1 input 1
[0] Thread is from /etc/motion/thread7.conf
[1] Thread started
[0] motion-httpd/3.2.6 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 9090
[0] Waiting for threads to finish, pid: 2880
[1] Started stream webcam server in port 8087
[1] Video signal re-acquired
[1] Raw changes:     0 - changes after 'EedDl':     0 - labels:   0 - noise level: 22
Errore di virgola mobile

Environment

Motion version:	3.2.6
ffmpeg version:	0.4.9-pre1, build 4747
Shared libraries:	ffmpeg, mysql, postgresql
Server OS:	Debian, kernel 2.4

-- GianMarcoArtioli - 04 Sep 2006

Follow up

This is not really a real bug. Width and height cannot be altered while Motion runs because it would requires quite a lot of reinitializing of everything internally in Motion.

Another problem is when you resize you have temporarily an illegal dimension which makes the driver spit and fail simply because the height and width are changed one at a time. So if a frame is read between the two settings the driver dies and then Motion dies.

To edit these parameters you have to change the config file and then restart Motion.

Maybe we should consider changing the way Motion behaves when you change width and height so that the settings can be saved to config and then enabled by restarting Motion from the web interface.

The failure to restart can be because you have illegal width and height in config file. The numbers must be supported by the camera device driver.

-- KennethLavrsen - 05 Sep 2006

Fix record

Closed , test with motion 3.2.10 and reopen it if you can reproduce again.

-- AngelCarpintero - 10 May 2008