Ben Noordhuis 98db7babcc test: fix pummel/test-net-connect-memleak ...

* Run the garbage collector before creating the big array. It doesn't
  matter now but if in the future something in node.js core creates
  a lot of reclaimable garbage, that will break the test's expectation.

* The first RSS check was being done too late. The garbage collector
  might have run before the check, throwing off the 'reclaimed memory'
  calculation.

* Due to changes in how V8 represents the big array internally, the
  actual memory usage is just below 256 MB on x64. Update the test's
  expectation.

2013-08-01 16:07:46 +02:00

..

addons

test: modify async native test.js to test for #4820

2013-02-21 13:14:07 -08:00

disabled

Merge remote-tracking branch 'ry/v0.8' into master

2013-02-18 10:21:08 -08:00

fixtures

debugger: breakpoints in scripts not loaded yet

2013-05-02 08:52:58 +02:00

gc

test: use the debug build of node-weak when necessary

2012-06-13 17:58:28 -07:00

internet

test: move two tests from simple/ to internet/

2013-07-20 12:36:33 +02:00

message

process: separate nextTick domain logic

2013-02-27 16:37:10 -08:00

pummel

test: fix pummel/test-net-connect-memleak

2013-08-01 16:07:46 +02:00

simple

events: fix memory leak, don't leak event names

2013-08-01 14:52:06 +02:00

common.js

test: optionally set common.PORT via env variable

2013-03-02 19:09:39 +01:00