[Motion-user] Segmentation fault

[Chris <mot...@go...>]

Hi,

I am running motion on raspbian (Linux raspberrypi 4.9.80-v7+ #1098
SMP Fri Mar 9 19:11:42 GMT 2018 armv7l GNU/Linux)

And am getting very often Segmentation fault:

$ motion -d 9
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
/etc/motion/motion.conf
[0:motion] [ALR] [ALL] conf_cmdparse: Unknown config option "duplicated"
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
/etc/motion/camera1-dist.conf
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
/etc/motion/camera2-dist.conf
[0:motion] [ALR] [ALL] read_camera_dir: Camera directory config
/etc/conf.d not found: No such file or directory
[0:motion] [NTC] [ALL] motion_startup: Motion 4.0 Started
[0:motion] [NTC] [ALL] motion_startup: Logging to file
(/var/log/motion/motion.log)
Segmentation fault

in the motion.log I noticed this:
[2:ml2] [DBG] [ALL] [Mar 23 16:40:09] motion_loop: Setup post capture 0
[1:ml1] [NTC] [EVT] [Mar 23 16:40:09] event_newfile: File of type 1
saved to: /var/lib/motion/CAM1_11-20180323164000-00.jpg
[2:ml2] [NTC] [EVT] [Mar 23 16:40:09] event_newfile: File of type 1
saved to: /var/lib/motion/CAM2_33-20180323164008-01.jpg
[2:nc2] [INF] [NET] [Mar 23 16:40:09] netcam_check_content_type:
Content-type image/jpeg
[2:nc2] [INF] [NET] [Mar 23 16:40:09] netcam_check_content_length:
Content-Length -1
[2:nc2] [INF] [NET] [Mar 23 16:40:09] netcam_check_content_length:
Content-Length 201138
[2:nc2] [INF] [NET] [Mar 23 16:40:09] netcam_read_next_header: Found
image header record
[2:nc2] [DBG] [NET] [Mar 23 16:40:10] netcam_read_html_jpeg: Potential
split boundary - 2895 chars flushed, 1 re-positioned
[2:nc2] [DBG] [NET] [Mar 23 16:40:10] netcam_image_read_complete:
Calculated frame time 318228.625000
[1:ml1] [DBG] [VID] [Mar 23 16:40:10] v4l2_next: 1) vid_source->pframe 0
[1:ml1] [DBG] [VID] [Mar 23 16:40:10] v4l2_next: 2) vid_source->pframe 0
[1:ml1] [DBG] [VID] [Mar 23 16:40:10] v4l2_next: 3) vid_source->pframe
1 vid_source->buf.index 1
[1:ml1] [DBG] [VID] [Mar 23 16:40:10] v4l2_next:
vid_source->buf.bytesused 1843200
[1:ml1] [DBG] [VID] [Mar 23 16:40:10] v4l2_next: the_buffer index 1
Address (6b947000)
[2:ml2] [ERR] [ENC] [Mar 23 16:40:10] ffmpeg_avcodec_log: Too large
number of skipped frames 60361 > 60000
[2:ml2] [ERR] [ENC] [Mar 23 16:40:10] ffmpeg_put_frame: Error while
writing video frame: Connection reset by peer
[2:ml2] [NTC] [ALL] [Mar 23 16:40:10] motion_loop: Thread exiting
[2:ml2] [NTC] [STR] [Mar 23 16:40:10] stream_stop: Closing
motion-stream listen socket & active motion-stream sockets
[2:ml2] [NTC] [STR] [Mar 23 16:40:10] stream_stop: Closed
motion-stream listen socket & active motion-stream sockets

The 4th and 5th line from bottom with ERRor:
ffmpeg_avcodec_log: Too large number of skipped frames 60361 > 60000
ffmpeg_put_frame: Error while writing video frame: Connection reset by peer


Is this the reason of Seg fault and how to resolve it?

thanks,
Chris