Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Support]: Possible memory leak

See original GitHub issue

Describe the problem you are having

I have a 5 camera setup. Frigate is running in Docker in an Ubuntu 22.04 container running on Proxmox 7.2-4.

I have to manually restart the container every few days / possible memory leak - see Proxmox memory usage…

image

Version

0.10.1-83481af

Frigate config file

mqtt:
  <configured correctly>

database:
  path: /media/frigate/frigate.db

cameras:
  Reolink-RLC511W-1: 
    ffmpeg:
      inputs:
        - path: <correct rtsp://>
          roles:
            - detect
            - rtmp
        #            - clips
        - path: <correct rtsp://>
          roles:
            - record
    #    width: 640
    #    height: 480
    #    fps: 7
    objects:
      track:
        - person
        - dog
        - cat
    motion:
      mask:
        - 0,0,1280,0,1280,359,0,340
        - 953,625,1280,616,1280,720,0,720,0,343,105,380,113,514,251,543,413,584

  Reolink-RLC511W-2: 
    ffmpeg:
      inputs:
        - path: <correct rtsp://>
          roles:
            - detect
            - rtmp
        #            - clips
        - path: rtsp://admin:Reolink1@10.0.1.213:554/h264Preview_01_main
          roles:
            - record
    #    width: 640
    #    height: 480
    #    fps: 7
    objects:
      track:
        - person
        - dog
        - bicycle
        - cat
    motion:
      mask:
        - 0,0,904,0,1280,0,1280,158,685,143,603,141,56,720,0,720

  Reolink-RLC410W-1: 
    ffmpeg:
      inputs:
        - path: <correct rtsp://>
          roles:
            - detect
            - rtmp
        #            - clips
        - path: <correct rtsp://>
          roles:
            - record
    #    width: 640
    #    height: 480
    #    fps: 7
    objects:
      track:
        - person
        - dog
        - bicycle
        - cat
  #    motion:
  #      mask:
  #        - 314,0,0,0,0,720,316,720
  #        - 1280,720,1280,503,635,720

  Enterance:
    ffmpeg:
      inputs:
        - path: <correct rtsp://>
          roles:
            - detect
            - rtmp
        - path: <correct rtsp://>
          roles:
            - record
    objects:
      track:
        - person
        - dog
        - bicycle
        - cat

  Intercom: # intercom
    ffmpeg:
      inputs:
        - path: <correct rtsp://>
          roles:
            - detect
            - rtmp
            - record
    objects:
      track:
        - person
        - dog
        - bicycle
        - cat

record:
  enabled: True
  events:
    retain:
      default: 5
    pre_capture: 5
    post_capture: 25

detectors:
  cpu1:
    type: cpu
    num_threads: 4

snapshots:
  enabled: True
  timestamp: True
  retain:
    default: 5

rtmp:
  enabled: false

Relevant log output

[2022-06-03 08:49:00] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:49:00] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:49:10] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x55a8af644980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:49:10] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:49:10] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:49:10] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:49:20] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x55fca5e30980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:49:20] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:49:20] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:49:20] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:49:30] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x55caa2cc6980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:49:30] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:49:30] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:49:30] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:49:40] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x55b665db5980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:49:40] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:49:40] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:49:40] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:49:50] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x560c9bd20980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:49:50] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:49:50] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:49:50] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:50:00] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x55eac7b40980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:50:00] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:50:00] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:50:00] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...
[2022-06-03 08:50:10] ffmpeg.Reolink-RLC410W-1.record ERROR   : [rtsp @ 0x56271923d980] method DESCRIBE failed: 401 Unauthorized
[2022-06-03 08:50:10] ffmpeg.Reolink-RLC410W-1.record ERROR   : rtsp://<correct rsp scream>: Server returned 401 Unauthorized (authorization failed)
[2022-06-03 08:50:10] watchdog.Reolink-RLC410W-1     INFO    : Terminating the existing ffmpeg process...
[2022-06-03 08:50:10] watchdog.Reolink-RLC410W-1     INFO    : Waiting for ffmpeg to exit gracefully...

FFprobe output from your camera

no issue with cameras, they are all working flawlessly & accurately detecting what they should be.

Frigate stats

No response

Operating system

Other

Install method

Docker CLI

Coral version

CPU (no coral)

Network connection

Mixed

Camera make and model

Reolink 511, 410 (wireless) and some (wired) IP intercom

Any other information that may be helpful

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:47 (17 by maintainers)

github_iconTop GitHub Comments

2reactions
NickM-27commented, Jun 30, 2022

There’s been quite a few users in this thread that reported some memory leak like behavior and there are a lot of differences between them (some on beta, some on 0.10, some seeing it in tmp/cache, some seeing it in the ffmpeg process, different kinds of hwaccel, etc) so it seems to me there likely won’t be a clear cut answer. A different version of ffmpeg will be used in the next beta release that should hopefully fix this for those seeing ffmpeg process memory issues on the beta

1reaction
pdobrien3commented, Jul 3, 2022

appears that the new beta release fixed my memory issues

Read more comments on GitHub >

github_iconTop Results From Across the Web

Webroot Support - Webroot Knowledge Base
Memory leaks are when programs on the computer incorrectly manage memory allocations. This is not uncommon on modern software and can cause performance...
Read more >
Memory leak / Handle leak | Firefox Support Forum
Here is a fairly simple explanation for a memory leak: A Memory leak occurs when your computer closes an open program and that...
Read more >
How To Fix Windows 10 Memory Leaks - Online Tech Tips
A Windows 10 memory leak occurs when an app you were using didn't return the resources to your system when you finished using...
Read more >
Possible Memory Leak? - Microsoft Community
Method 2. Run memory diagnostic tool: The memory diagnostic tool is a RAM test to check if there are any issues with RAM....
Read more >
How do I check for memory leaks, and what should I do to stop ...
Despite having adequate RAM and not running resource-intensive software, there can be another situation where all available RAM gets used and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

[Support]: Getting Your config file is not valid! error

Next page

[Support]: Is it possible to access Frigate Docker Container instance via Home Assistant via a proxy (not an addon)