https://bugzilla.wikimedia.org/show_bug.cgi?id=53776
--- Comment #5 from Marc Ordinas i Llopis <marc...@wikimedia.org> --- I did detect some amount of memory leakage while profiling locally, if I recall correctly, ~90k per fetch/results cycle. As I mentioned in a previous comment, the leakage seemed to come from not-released arrays of "code deoptimization_data". If I remember correctly V8's arch that could come from virtual method calls over many different implementations, debugging/profiling artifacts, or a few other things. And of course it could be our code or some library leaking closures, but I think those would show up differently, especially if the code is used only once. That's where profiling took me… I'm a little stumped of what to try next, but I think that I'll make a small test case to check it's not the mysql library. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
