It's explicitly to help a debugger. Best to not use that option except when debugging. (It disables certain bytecode patterns that help to avoid OutOfMemory errors)
On Monday, January 25, 2016 at 1:49:03 AM UTC-5, Mars0i wrote: > > In my application, I seem to get a memory leak when I use > -Dclojure.compiler.disable-locals-clearing=true in Clojure 1.7.0 and 1.8.0, > but not in 1.6.0. (i.e. I get "java.lang.OutOfMemoryError: GC overhead > limit exceeded" with the more recent versions). > > Any guesses about why this might happen? Just curious. > > (I think I can live without disabling locals-clearing. I don't fully > understand it. Not sure why I started using it. I don't use a debugger.) > -- 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 Note that posts from new members are moderated - please be patient with your first post. 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
