BUG: Memory allocation error

Message from syslogd@tux at Jun 23 10:58:24 ...

motion: [1] Could not allocate 284467200 bytes of memory!: Cannot allocate memory

mysql-5.0.51a-1.fc9.i386

ffmpeg-0.4.9-0.45.20080113.lvn9.i386

postgresql-8.3.3-2.fc9.i386

SVN - Updated to revision 368.

   *********************
     Configure status    
      motion 3.2.10.1
   *********************

OS             :     Linux
pthread Support:     Yes
jpeg Support:        Yes
mjpeg Support:       Yes
V4L included:        Yes
V4L2 supported:      Yes
FFmpeg Support:      Yes
MYSQL Support:       Yes
PostgreSQL Support:  Yes

'free' shows:
             total       used       free     shared    buffers     cached
Mem:       1034860     277892     756968          0       2004      61980
-/+ buffers/cache:     213908     820952
Swap:      2031608     274916    1756692

Compiles without errors. Every time I try to run motion, I get the "Could not allocate 284467200 bytes of memory!" error within 30 seconds.

mysql-5.0.51a-1.fc9.i386
ffmpeg-0.4.9-0.45.20080113.lvn9.i386
postgresql-8.3.3-2.fc9.i386
libcurl-7.18.2-1.fc9.i386

Environment

Motion version:	3.2.10.1
ffmpeg version:	ffmpeg-0.4.9-0.45.20080113.lvn9.i386
Shared libraries:	ffmpeg, mysql, postgresql, libcurl
Server OS:	Fedora 9 - 2.6.25.6-55.fc9.i686

-- TateB - 23 Jun 2008

Follow up

Please add your config files.

-- AngelCarpintero - 24 Jun 2008

Fix record

This is not a bug - rather an ID-10-T user error.

Mis-type in motion.conf resulted in configured resolution of 640x444480 - no wonder it was having issues.

Re-configured to correct values of 640x480 and it works as expected - very well.

Sorry for the hassle and thanks for your time.

---

Thanks ! Ok i won't happen in future with config range values implementation.

-- AngelCarpintero - 27 Jun 2008