I ran to into some strange agent behavior today that may be a bug. An agent apparently exhausted the JVM available memory and threw an OutOfMemoryError -- but it didn't go anywhere. I saw the error in the console, but I couldn't get at it from the REPL: agent-errors still returned nil and .getQueueCount still returned 1. clojure.contrib.stacktrace/e did not report it as the most recent exception. What's more, the agent is now a "zombie" in that subsequent sends fail silently (they do inc the queue count, but it seems the memory-eating action is stuck). Chouser has a succinct test case at http://paste.lisp.org/display/73224, with my annotations.
Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
