Hi!
Maybe this is related:
https://github.com/einaros/ws/issues/43
Some users experience high RSS usage which does not shrink. Maybe node
fails to properly free RSS memory used by buffers, so the process will use
all memory it can get over the time (some days), though it does not crash
but hav
Am 17.09.2012 um 06:42 schrieb Ben Noordhuis :
> On Sun, Sep 16, 2012 at 9:55 PM, Brian Gruber wrote:
>> It also appear that RSS grows to fill up available memory but doesn't seem to
>> hit an OOM. It just stays at a very high memory usage.
>> ...
>
> That's intentional. The V8 garbage collecto
Am 13.09.2012 um 10:05 schrieb Stefan Zehe :
> i solved my problems with an update to 0.8.9.
>
> in 0.8.3 there was a bugfix
>
> > events: Fix memory leak from removeAllListeners (Nathan Rajlich)
>
> which might caused a steady growing _events-array.
I'll check if I can get information about
e the culprit.
Nico
Am 12.09.2012 um 02:58 schrieb wavded :
> Nico did you have any luck in your debugging adventures? My symptoms seems
> to very closely match yours. Was going to try mtrace.
>
> On Monday, March 19, 2012 11:52:34 AM UTC-5, Nico Kaiser wrote:
> Thanks Ilya, I&#
hrieb Ilya Dmitrichenko:
>
> On 19 March 2012 14:09, Nico Kaiser wrote:
> > How can I debug this behavior? I tried node-inspector, but v8-profiler
> only
> > works with Node 0.4. Running node-gc every few seconds smoothes the
> memory
> > curve, but does not help any
Hi!
For some months I'm desperately searching for a memory leak in my Node
server.
It's a simple publish/subscribe WebSocket server that serves about
15-20.000 concurrent clients.
With Node 0.4 and miksago's node-websocket-server library the memory
consumption was ok, and the memory was fre
Well, forever does not help when you not only need something that restarts
the script on error, but a real startup script (which starts the node
service when the server reboots).
I wrote a simple init script for this purpose (with logging and user
switching) for sysvinit: https://github.com/nic
