Some fixes require a lot of investigation and this is one of them. The memory leak that we reproduced was related to the size of tabs in sub-editors (such as blueprints with lots of functions open). When the tab gets so small that the text has to be culled, a memory leak begins to occur. We believe that this is what some, but maybe not all, of you are encountering.
Thank you for your patience on this. It’s been a difficult one to track down and we are still trying to get it resolved.