Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: mozek who wrote (33232)	6/30/2000 2:15:13 PM
From: Prognosticator	Read Replies (1) \| Respond to of 64865

You're right, in theory. A real operating system would reclaim all memory allocated to a process once the process is terminated. What I see is, however, that after a day of hard work, launching many processes and Java compilations/executions, that the total memory allocated is much less than the sum of mem usage of all processes. Killing off every user process still leaves 50-100 MB of memory unaccounted for, hence kernel leaks. So my machine ends up thrashing the disk paging like crazy, and becomes unusable. It's so bad I don't think that the word 'Professional' should be allowed on the box. P. Rather than reboot, you should be able to use the task manager and kill the process to reclaim the memory. In case you still care, I'm using the VM which comes with JBuilder, which is a 1.2.2 derived version.