Stefano Bagnara wrote: > Where did you read that mysql recommend to downgrade to 2.0.14 > as a workaround for memory leaks?
See http://bugs.mysql.com/bug.php?id=20003, particularly the second paragraph of the author's response. >> Let me rephrase that: as I had said in the original post, it was really >> quite stable for the better part of a week, just as my current process has >> been really stable at 113MB since Monday. I was pretty pleased and >> confident. But then last weekend, the "JVM process size [grew] from a >> stable 114MB to 130MB" by Sunday night, and died early Monday morning after >> 10 days or so over non-stop operation. > Any idea about what could have been changed from monday to sunday? This > would indicate that the leak is not on common code but in operations > that have been only called in the latest days.. Nothing comes to mind. And interestingly, the memory for the current JVM process just jumped from 113MB to 116MB since last night. I'm going to see what happens over the next day, and when I restart it, I'll restart with heap profiling enabled. > you say that you have a very low limit on the message size so we could > exclude it. A few MB maximum. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
