Page MenuHomeSoftware Heritage

Memory leak in
Closed, WontfixPublic


There's a memory leak somewere in the stack.

We can mitigate it by setting gunicorn to reap workers after a set number of queries, but it's a pretty ugly thing to do.

Let's try to investigate and fix it...

Event Timeline

olasd created this task.Sep 11 2017, 12:15 PM
ardumont renamed this task from Memroy leak in to Memory leak in 11 2017, 4:37 PM
zack raised the priority of this task from Normal to High.Jun 19 2018, 2:34 PM

Is this still "a thing"?

olasd closed this task as Wontfix.Jan 23 2020, 2:10 PM
olasd claimed this task.

Considering the age of the bug report and how many underlying libraries have been upgraded, we can reopen this when we notice it again.