Hi All! I have an application that suffers performance degradation over time. Memory also increases slowly, as does the mark/sweep time, increasing from 2ms to >25ms. Now I have had this problem before and the cause was undisposed persistent handles, apparently bogging down the GC. I eventually tracked that down but this time I cannot find the cause. One thing worth noting is my memory leak detector did not detect the undisposed persistent handles. So I don't know how far to trust it this time, should it have found them? Or would the inner workings of V8 hide this leak somehow? I'm on Windows, Valgrind is sadly not an option.
Is there a way to dump information about the storage cells, and the number of active persistent handles? Thank you, Stuart. -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
