There is no ticket or heap dump available. As usual with memory leaks it's very hard to pinpoint the cause. So you can just wait or try upgrading and watch memory consumption (i've been checking JVM peak memory once per day and it grew to 400 MB in a few days, in 6 days it stalled, when it was running fine for 30 days on 3.9.1, though still coming to a stall after a month). There was a leak in 3.9.1 (or even earlier version), but now it is leaking faster. Maybe it is even the same leak, but now its effect is tripled because of some recent changes in the code.
↧