Bote + IMAP => OOM

[killyourtv]

I don't know if this is a known problem, but navigating I2P-Bote with IMAP triggers an OOM.

I don't know (yet) if it's a specific folder causing it or a specific message, but I do have a heap dump that was generated at the time of the OOM in case it's be of use.

The largest retained objects are in i2p.bote.folder.EmailFolder.

(This is with I2P-Bote in trunk, currently rev ​586515162c23d6374d92552e7433e47207e52edd)

[zab]

A heap dump is the best/only way to properly debug this. However, you want to make sure there is no sensitive information in the dump. That means you should use a separate instance of the jvm with only Bote in it, and you should use a throwaway Bote identity.

[killyourtv]

I'll set up a Debian unstable VM (with throwaway IDs) and try reproducing this problem in the virtualized environment.

[killyourtv]

With current trunk I can still reproduce the OOM in my normal installation.

I have not yet been able to reproduce it in my test virtual machine.

[killyourtv]

visualvm

[str4d]

My suspicion is that i2p.bote.imap.MapperFactory.getMailboxes() was causing this problem; the BoteMailboxes were not cached, but each one registers a FolderListener with its underlying EmailFolder. I believe this caused them to never be GCed. I am not sure why EmailFolder is the one that shows up as the largest retained objects, there should only ever be four (inbox, outbox, sent and trash).

Please try latest trunk, which caches BoteMailboxes.

[killyourtv]

It's been about a week and it looks like the OOMs that I was seeing are gone. :)