is http://cursive-ide.com down ?

@cfleming

@yusup I think it’s ok - what are you seeing?

unable to connect

weird, I am from China and I use socks proxy for everything.

Youtube, Twitter all works fine, but not http://cursive-ide.com

I can access http://cursive-ide.com without socks proxy.

Yesterday, there was no such issue.

I tried curl on my VPS. It failed with connection refused. Maybe this is related to my VPS(Google Compute Engine).

my bad.

@yusup Hmm, I’m not sure. I just moved my website from my own server to AWS, perhaps that change caused your issue.

I can access without proxy , so all good. 🙂

I have a weird problem. I have a namespace, which seems not to be compiled on start. When I try refresh the namespace in cursive, the error of missing javaclass is thrown. Now I have to recursively have to go through each dependency and reload the file in cursive. It is only for this namespace and its dependencies. All other are loaded normally. Currently the namespace isn't a dependency in the project, if this helps.

Ah, a directory had a - not a _.

Okay this is unexpected. Should my REPL process be able to hang IDEA itself?

I'm using a Lein REPL within Cursive (macOS 10.12.2)

I'm rewriting some code that was blowing the heap in the REPL and now it appears (i'm not sure what else could have done it) to have beachballed IDEA itself

odd, it seems like it's using IDEA VM memory

there's something going on here that i don't understand

So cursive is still informing me of “errors” when I use transducers. For example, I have a comp and one of its args is (mapcat vals).

Cursive highlights (via red underline) the mapcat with an “Incorrect arity” message

Though I just realized it’s telling me incorrect arity for cljs.core/mapcat…which might just mean I have to update my cljs and this has nothing to do with cursive...

Yeah, that was it. Don’t mind me...

@danielgrosse Ugh, sorry, I’ve been meaning to create an inspection for that.

@sandbags That sounds strange - which Cursive version are you on?

There were a couple of memory leaks fixed a while back, but this might be another one.

@cfleming i am on 1.4.3-2016.3

i mean, it seems clear to me that i am missing something about memory management/GC and maybe I am creating a lot of short-lived objects and starving the GC

because i've blown the heap several times with this code and... i don't think i should have

@sandbags Ok, you have those fixes then. Do you see the memory use going wild in IntelliJ itself? You can show a memory indicator by going to Settings->Appearance & Behaviour->Appearance->Show memory indicator. That will show a memory use graph at the bottom right, and you can provoke a GC by clicking on it. When the problem occurs, if you see that memory indicator showing most of your memory being used and clicking on it doesn’t manage to free much, then a memory leak (or just high memory use of some kind) is almost certainly the problem.

i've switched to accumulating frequencies at a lower-level rather than allowing 22 million element lists to build up

but even then memory built up rather than staying flat

But like you say, that shouldn’t affect IntelliJ.

well that was the odd thing, i even got a warning dialog from intellij asking me to up the heap size

it created the .vmoptions file thingy

yet i wouldn't imagine code running in the REPL should have any effect on the IDEA process, unless there is something about the debug invocation that is conflating them somehow

but i should have thought that was just about some kind of trace diagnostics in the VM

@sandbags Ok, if IntelliJ warns you then there could well be a memory leak. The ones I fixed recently were in the REPL client and in the REPL output display area.

Can you take a heap dump when the problem is occurring?

Ah perhaps so

well unfortunately i've modified the code since then to keep heap usage to an absolute minimum

But again, that’s in your process, not IntelliJ

since i was also blowing the heap of the JVM

Ah ok

Well, if you see the problem again, try to get a heap dump from the IntelliJ process and we can take a look at it.

https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems

will do

It might be a good idea to add those options now so you’re ready if you see the problem again.

done

& thanks