I don't think it is possible to define a way to deal with heap saturation that is general enough to cover all programs written in Clojure, and therefor I don't think this is something that the Clojure runtime should deal with at all.
Personally, I only know of two ways to handle OutOfMemoryErrors: 1) let the program blow up and hope someone notices or 2) look at your body, pick the limb you are least likely to be needing pretty soon and cut it off (aka. free some memory) and _then_ yell for help through some hopefully reliable channel. On Sat, Jan 10, 2009 at 9:03 PM, Paul Mooser <taron...@gmail.com> wrote: > > After talking to Jeffrey Chu, it seems like what is actually happening > is possibly fairly obvious (in retrospect) - the java process runs out > of heap space, and there's not even enough memory to keep swank- > clojure working properly. Jeffrey tried some examples with just a > plain REPL (without SLIME), and managed to get a dead REPL after > causing an out of memory error, so there may be more fundamental lower > level things going on, and it's not clear that this can really be > addressed on the SLIME side. > > I'm not sure what a good solution to this problem would be, but I > thought I'd post an update for anyone who was curious what the actual > issue was. > > > > -- Venlig hilsen / Kind regards, Christian Vest Hansen. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
