motioneye-project/motioneye

Web interface slowing down when viewing lots of next pictures in picture browser

Open

#2,214 opened on Oct 23, 2021

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import
help wantedquestion

Description

Hi.

I frequently look at events by going to the picture browser, select the directory, the first picture of interest, and then fast-forward with the right key or the right button to see the next pictures.

Unfortunately, the interface begins to slow down after about 50 pics, and is unusable after about 100 pics. I'm using Firefox.

Closing the current picture view and reopening a new one on the same current picture fixes the problem temporarily... until the next 50-100 or so pictures.

My guess would be that the pictures or the picture loaders are not properly freed until image view close, but I'm not a javascript expert.

Config: Raspberry Pi 4 8GB Raspbian 10 MotionEye 4.3.2 Motion 4.3.2 Image File Name: %Y%m%d/%v/%H-%M-%S-%q Storage: Kingston A400 SSD SA400M8/240G M.2 2280 with Argon ONE M.2 case

Regards,

Contributor guide

Tech stack
javascript
Domain
frontendperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScript fundamentalsbrowser developer tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the picture viewer component in the web interface for memory leaks. Check if images are being freed when navigating away. Use browser developer tools to profile memory and identify objects that are not garbage collected. Look at the JavaScript code handling image loading and navigation. The user suggests that images might not be properly freed until the view is closed.