At the bonsai URL above, is a point where an orkinHeap is being allocated which leaks. I'm guessing this leaks because you are creating a new one here, and the morkEnv that gets created with it doesn't seem to be deleting it when it goes away. So the ownership of the orkinHeap is unclear to me.

Reassigning.

accepting, but doubt will be fixed.

moving to future milestone.

Can we afford for this to remain futured? If nothing else, apart from the mail/news usage, mork does get used in global history, impacting the rest of the product.

It's a one-time leak, i.e., constant overhead per db opened. Since we only open the history db once at startup, and close it on shutdown, there's nothing to be gained by fixing this leak, except cutting down the noise so we can see the real leaks.

changing priorities

If this isn't a big leak then marking nsbeta1-

David, I filed bug 96383, which is a DUP of this bug, but it has more explicit information. Which way do you prefer the DUPing go? Thanks.

Rather, I meant bug 96379, sorry.

Stephen, I'm not sure they are dups - this is for leaking the orkin heap proper (which is a small object), and the other is for leaking a rather larger object (a file store) allocated from the orkin heap.

plussing; will be fixed when mork changes land.

fix checked in

Verified FIXED. Nice job, David. I launched mail with a 5 msg IMAP Inbox, then read a message. This used to show up for every mail/news operation I did. Now, I'm not seeing it.