Search:

I think I have all I need at this point, and I'm willing to call this problem solved. I know why the memory bloat was occurring and what I can do to prevent it. Thank you kindly, everybody :)

I don't need to zero data at all, and I intend to remove rows from both lists as I match them up. As a point of fact, I may not even need a third list. It should be simple enough to just update the...

It would normally be a pretty simple problem, but I'm trying to devise a software package that will work with a wider range of data than JUST the two files I'm given in case my project manager wants...

*edit*
4 AM, and my brain is slowing down :)

What's causing the OutOfMemoryEorror is the code I listed in this post, specifically the second loop. It's a mirror of what I was doing at work, and...

I did try that, though I didn't mention it for fear of making an even bigger fool of myself :) In nearly all cases, Garbage Collection does shave around 20MB off the used memory, so it's clearly...

*sigh*
Some days I pine for C++ and its EXPLICIT pointer invocations... But then I remember how much of a tangled mess I made of those and resign myself to just try and anticipate what Java does. So...

OK, show of hands - that I was simply creating more references to the SAME ArrayList completely skipped my mind, and that would indeed explain a lot of the differences. I'll need to come up with a...

Correction - that OutOfMemoryException is actually a java.lang.OutOfMemoryError: Java heap space. What caused it is the following, and this will probably make me look really unprofessional and...

I actually considered that mayby totalMemory is reporting false results and would have chalked it up to that, but my strongest evidence for the discrepancy is that the second loop will run out of...

I apologise for jumping right into a question, but I ran into the sort of behaviour that just makes no sense to me. It's like looking into the face of Great Cthulu - it's something that should not...