Found a new bug and it's a head-scratcher. Autocomplete quit working
sometime overnight. Now I get a SocketException message "Software
caused connection abort" if I hit control-space at the REPL. REPL
process is connected OK -- I can evaluate forms at it -- so it's not
the REPL-to-Eclipse socket connection that's failed. Firewall and
Wireshark type tools show nothing unusual on the internet uplink, so
it looks to be some other use of the loopback interface that's
b0rking.

Weird.

In a related development, the Namespace Browser is blank and has been
for a while. I had a long-running calculation last night evaluating at
the REPL during which it blanked and came back. I think it may have
blanked again and then failed to come back. This was while I was
investigating the head-holding issue with apply and arguments
containing embedded lazy seqs. I think it might be related to this odd
exception trace I got for one of those, where the OOME apparently got
thrown into a different thread in the JVM:

java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
Java heap space
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232)
        at java.util.concurrent.FutureTask.get(FutureTask.java:91)
        at clojure.tools.nrepl$handle_response.invoke(nrepl.clj:263)
        at clojure.tools.nrepl$message_dispatch$fn__179.invoke(nrepl.clj:303)
        at clojure.lang.AFn.call(AFn.java:18)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.OutOfMemoryError: Java heap space

Restarting the REPL process fixed both problems (the Namespace Browser
remained blank until a mousemove event was generated within its
bounding box, then promptly filled in).

I'm not sure if the OOME caused it. If not, then it looks like the
problem is something that can get into a bogus state over on the REPL
process side. Does CCW open two separate connections to the REPL
process, one for evaluations and one for introspecting into the
namespaces and other state of the session?

-- 
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

Reply via email to