Getting OutOfMemoryErrors in some cases about littleproxy

[leahxschmidt]

This is caused by some sort of leak with JMX. I'm investigating the JMX story a bit further, but if you want to temporarily patch it, just comment out HttpRequestHandler.java line 215.

[leahxschmidt]

Pull request #51 fixes this.

[adamfisk]

The only odd part about this is that JMX is disabled by default.

[leahxschmidt]

I checked littleproxy.properties, and JMX is in fact enabled by default.

[md-5]

Should probably disabled it by default in this PR

[adamfisk]

Hmn..yes it is -- we should definitely change that. How is that causing OOME?

[leahxschmidt]

Apparently, JMX is retaining references to the HttpRequestHandlers. I looked in VisualVM, saw the memory usage rising (even after a forced GC), and looked at what object was largest. Tracing from there got me to the leak.

It would be nice if there were a way to do weak refs in JMX, but I couldn't see how.

[adamfisk]

Very interesting - makes sense. I'll apply the patch, and we'll go from
there! Thank you sir.

On Tuesday, December 18, 2012, Leah X Schmidt wrote:

Apparently, JMX is retaining references to the HttpRequestHandlers. I
looked in VisualVM, saw the memory usage rising (even after a forced GC),
and looked at what object was largest. Tracing from there got me to the
leak.

It would be nice if there were a way to do weak refs in JMX, but I
couldn't see how.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-11471418.

Sent from Gmail Mobile

[leahxschmidt]

Ma'am.