Comment 44 for bug 1672297

It might be more complicated to fix as there are lots and lots of actions that get to memory leaks. There are some crashes, too. Bad programming, probably, and it might need some fundamental changes in the code and architecture. They are creating lists and objects that are larger and larger on each trigger, without killing any when they are not needed or having a limit to recycle resources. And if they got to this, it might be complicated to find solutions with the same team that created it. I kind of doubt we'll see a solution before the next release.