Motion crashes unexpectedly

Bug #1240237 reported by Gabriele Tozzi
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
motion (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm running motion on an updated 24/7 server with many other processes and no suspected hardware problems.

I'm using motion to collect data from an IP camera.
I'm also using another software to connect automatically to motion's web port on localhost and check the camera is alive.
Motion runs smoothly for hours, sometimes days.

Sometimes (let's say 2-3 times a week), motion crashes. That's what I found on syslog:

    Oct 15 05:22:59 transylvania motion: [0] Thread 1 - Watchdog timeout, trying to do a graceful restart
    Oct 15 05:23:10 transylvania motion: [1] Calling vid_close() from motion_cleanup
    Oct 15 05:23:11 transylvania motion: [1] vid_close: calling netcam_cleanup
    Oct 15 05:23:11 transylvania motion: [1] netcam camera handler: finish set, exiting
    Oct 15 05:23:11 transylvania motion: [0] Motion thread 1 restart
    Oct 15 05:23:11 transylvania motion: [1] Thread 1 started
    Oct 15 05:23:11 transylvania motion: [1] Resizing pre_capture buffer to 1 items
    Oct 15 05:23:19 transylvania kernel: [5717631.158791] motion[17206]: segfault at 131 ip 00007fa135bed248 sp 00007fa12d7b4438 error 4 in libjpeg.so.8.0.2[7fa135bb9000+3f000]

Talking with the guys on #motion, they said "libjpeg errors are often due to jpeg vs jpegturbo without a rebuild"... not sure if this info is useful.

Restarting motion makes it work again with no problems until next crash.

I'm attaching my motion.conf (comments removed for readability) and .crash file. If you need more info, please don't hesitate to ask.

Thank you.

----- System info ------

# lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

# apt-cache policy motion
motion:
  Installato: 3.2.12-3.4
  Candidato: 3.2.12-3.4
  Tabella versione:
 *** 3.2.12-3.4 0
        500 http://archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages
        100 /var/lib/dpkg/status

# apt-cache policy libjpeg8
libjpeg8:
  Installato: 8c-2ubuntu7
  Candidato: 8c-2ubuntu7
  Tabella versione:
 *** 8c-2ubuntu7 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

# apt-cache policy libjpeg-turbo8
libjpeg-turbo8:
  Installato: 1.2.1-0ubuntu2
  Candidato: 1.2.1-0ubuntu2
  Tabella versione:
 *** 1.2.1-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Gabriele Tozzi (gabriele-tozzi) wrote :
Revision history for this message
Gabriele Tozzi (gabriele-tozzi) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in motion (Ubuntu):
status: New → Confirmed
Revision history for this message
Pander (pander) wrote :

Probably, this has been fixed, see https://github.com/Motion-Project/motion/issues?q=is%3Aissue+is%3Aclosed+segfault

This was also reported for a version from 2013~2016 and is I think no longer relevant. If that is the case, this bug can be closed.

Changed in motion (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.