Annotator memory leak

Feedback
1

This is copied from this issue, but I have posted it here as it seems issues reported there are not looked at often

Describe the bug
After using the annotator with label assist for a while, the memory usage gets very large. The annotator becomes sluggish, eventually freezing altogether.
As said by narugo1992, windows does not crash. The memory leak still occurs on windows, but the annotator does not slow, freeze, or crash.

To Reproduce
Steps to reproduce the behavior:

  1. Open the annotator
  2. Enable Label Assist
  3. Annotate for a while

Expected behavior
The memory usage stays low, and the annotator does not slow down after time.

Evidence

image
image732×76 6.79 KB

Desktop (please complete the following information):

  • OS: Fedora 38
  • Browser: Google Chrome Version 115.0.5790.110 and Firefox 115.0.2
3

Hi @Alec_Jensen

Thank you for letting us know! We appreciate it. I’m going to change the category to Feedback and let the team know.

4

Update: it also crashes on windows, it just seems like windows has a higher memory limit before crashing.

5

Is this also related to really laggy labelling when there are 100+ labels on an image? (sometimes it takes multiple seconds when I click before it starts drawing a polygon) And is there a fix for this yet?

6

I don’t know if it’s related. But the problem still isn’t fixed.

7

Hey is there any update? This issue is still happening for me.

8

Hey, Alec, we’ve been aware of memory leaks — note: some isolated to Linux browsers — and delivered updates for many of them.

Here’s a summary of issues we isolated and pushed fixes for recently:

  1. The user’s browser doesn’t properly garbage collect
  2. WebGL contexts weren’t getting released
  3. SAM embeddings were being held
  4. Ctrl+Z history wasn’t bounded

Our team have been doing extensive memory leak debugging and fixes these last few weeks as well and has been able to verify with the profiler that memory usage no longer grows as you page through and annotate hundreds of images. This includes being able to scroll ~2000 images and not seeing any issues.

There is one known outstanding issue caused by react devtools. Disabling the chrome extension avoids this leak, should that affect you.

Can you confirm if your original message issue still persists for you?