cky: wow, I didn’t realize how much memory the slack app was sucking up. Using activity monitor, slack is #2 in the memory column (489.9 MB) behind kernel_task, and using “Real Mem” it’s #3 (660.2 MB) behind kernel_task and mds_stores

@badkins: Only 0.5 GB? Lucky you. I’ve had Slack use up 13 GB on a bad day.

Ouch - that has to be virtual size though, right?

Well yes, my MBP only has 4 GB physical memory.

I only have 4 slacks,a nd only 1 is very active

Hmm… Activity Monitor isn’t very explicit. Is the “Memory” column virtual ?

Probably not since it’s less than “Real Mem”

writes "" emty string even though if I call it with the same args from the commandline and 2>err.log the file will show something for stderr whereas the racket code doesnt

@cky here’s the thing I mentioned @IRC chat

Uh, your arglist is wrong.

That won’t capture anything.

Try this:

mmmh according to the docs the order is out in err-out

(call-with-output-string (lambda (p) ((fifth (apply process*/ports (current-output-port) (current-input-port) p “dialog” arglist)) ‘wait)))

where arglist contains everything after “dialog”.

Notice that I passed in p as the third argument of process*/ports and not (current-error-port).

since that’s what you wanted to capture.

ok gimme a sec

IT WORKED :boom: :party: but where in the docs does it say what the signature for the lambda is? call-with-output-string

oooooh proc : (output-port? . -> . any) I see .. alright yeah I’m not used to the racket docs yet

oh my god thank you so much! do you want me to post it on SO? How can I thank you for this xD?