Massive Memory Leak Caused by USB Connection

Question

I have a Sansa Fuze MP3 player.  I noticed when I connected it via USB both to an iMac 27" late 2009 and MacBook Pro 15-inch early 2011, both machines would grind to a halt. get very hot, and run the CPUs at full blast.  The Finder would quickly become unresponsive.  There were huge (like 500 GB) virtual memory files.  Disk Utility could not repair the drive.  Reformatting the MP3 player using its System menu finally cured the problem.  Seems like Lion should have a better way of handling misbehaving peripherals.

Answer 1

i forgot to include one line, but i didn't see why it made a difference:
ConcurrentMap<Connection, Boolean> connPool = this.createConnPool();
for(;;) {
  sok.receive(dgPak);
  ObjectInputStream ois = new ObjectInputStream(new ByteArrayInputStream(dgPak.getData()));
  MyInterface foo = (MyInterface) ois.readObject();
  foo.assignSharedMap(connPool);  // <-- forgot to include this one line.
  foo.doStuff();
  foo = null;
  System.gc();
}the number of de-serializations still equals the number of " +public void finalize();+ " invocations.
note: i never add new connections to the pool. it "looks" like a ConcurrentMap
does not allow objects that reference it to compleley die. (if this behaviour is as to be expected , my apologies, and could you explain a safe way for multiple objects to share a common Collection ?)
this code works fine:
for(;;) {
  sok.receive(dgPak);
  ObjectInputStream ois = new ObjectInputStream(new ByteArrayInputStream(dgPak.getData()));
  MyInterface foo = (MyInterface) ois.readObject();
  foo.doStuff();
  foo = null;
  System.gc();
}at this stage of de-bugging i could have tested with just a regular java.util.Map<Connection, Boolean> but forgot. i am using a
completely different approach now, so i'm not going back to test, though i bet it is related to java.util.concurrent. .