flutter in detections under review

[ThorstenUm]

I'm using version 0.16.2.

When I restart my PC, some detections don't seem to complete properly. It seems like a detection gets stuck between page displays under certain circumstances and can't be manually completed when new detections are available. Then the system starts flickering. See the video. This puts the system under 100% load. You can see the resulting logs on the other screen.

I couldn't get rid of the problem initially. The system calmed down when I navigated to a different page. If I went back, the detection was still stuck.

Only after displaying all the checked detections again and confirming them all was I able to resolve the issue.

Clip.mp4

Is this a known cause?

[inkeep-ai-assistant[bot]]

There is a discussion describing similar flickering or refreshing issues in the review section of Frigate, where the review screen enters a constant refresh loop and can result in high load(1). In that discussion, users observed rapid network activity or missing resources, and some noted that navigating away from the page stopped the issue, but returning would resume the flickering(1). Updating to a newer version was suggested, as running an older build could contribute to such problems. If updating does not resolve it, providing your configuration, logs, and system metrics is recommended for further troubleshooting(1).

📚 Sources:

1. Review detections cause a flickering/refreshing screen

---

Have another question? Just tag @inkeep.

[hawkeye217]

We've not had any other reports of this, but it just seems like your browser has cached something. You could try clearing the cache.

[ThorstenUm]

I restarted the browser and cleared the cache. That didn't help. I've had this problem before. I even completely reinstalled the system then. I dismissed it as an isolated incident. Something is obviously getting stuck in the pipeline during shutdown. It could also be related to when many new events are coming in and these aren't showing up in the review as new.

[hawkeye217]

Did you try another browser?

[ThorstenUm]

No, I hadn't tested another browser. It's also difficult to reproduce the behavior.