Program abort: out of memory: can't allocate 81946 bytes

[GoogleCodeExporter]

Hy there, 
I have a problem with running skipfish on a dedicated managed server, it fails 
after runnign 90 minutes with:
[-] PROGRAM ABORT : out of memory: can't allocate 81946 bytes
    Stop location : __DFL_ck_alloc(), alloc-inl.h:69

The commandline:
skipfish -W dictionaries/myown_keywords.wl -A myusername:mypassword -o 
../../skipfish-result-full/ http://myserver

The whole result is:

skipfish version 1.45b by <lcamtuf@google.com>

  - myserver -

Scan statistics:

      Scan time : 1:31:20.0189
  HTTP requests : 1458361 (266.1/s), 4111635 kB in, 474036 kB out (836.8 kB/s)
    Compression : 0 kB in, 0 kB out (0.0% gain)
    HTTP faults : 62 net errors, 0 proto errors, 15 retried, 0 drops
 TCP handshakes : 7365 total (198.2 req/conn)
     TCP faults : 0 failures, 0 timeouts, 1 purged
 External links : 22302 skipped
   Reqs pending : 1334

Database statistics:

         Pivots : 8925 total, 8663 done (97.06%)
    In progress : 192 pending, 47 init, 6 attacks, 17 dict
  Missing nodes : 169 spotted
     Node types : 2 serv, 80 dir, 594 file, 6448 pinfo, 306 unkn, 155 par, 1341 val
   Issues found : 2711 info, 58 warn, 1824 low, 5 medium, 5 high impact
      Dict size : 2433 words (1655 new), 29 extensions, 256 candidates
[-] PROGRAM ABORT : out of memory: can't allocate 81946 bytes
    Stop location : __DFL_ck_alloc(), alloc-inl.h:69

Do you need more information?

Best regards
Thomas

Original issue reported on code.google.com by thomas.l...@gmail.com on 1 Jul 2010 at 12:02

[GoogleCodeExporter]

Please check the output of these commands:

ulimit -a
free

...to see if the amount of memory available to the program is not artificially 
limited.

Also, what's on the site? Is it heavy with images / videos, you may want to use 
-s to limit sample size.

Original comment by lcam...@gmail.com on 1 Jul 2010 at 8:38

[GoogleCodeExporter]

Thank you for your answer.

:~ > ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) 65536
max nice                        (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 37376
max locked memory       (kbytes, -l) 262144
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
max rt priority                 (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) 259200
max user processes              (-u) 2000
virtual memory          (kbytes, -v) 262144
file locks                      (-x) unlimited

:~ > free
             total       used       free     shared    buffers     cached
Mem:       4075240    3479992     595248          0     255488    2703920
-/+ buffers/cache:     520584    3554656
Swap:       497992          0     497992

No, there aren't many images - yet.

Thank you.
Thomas

Original comment by thomas.l...@gmail.com on 2 Jul 2010 at 1:47

[GoogleCodeExporter]

Looks like the amount of per-process memory is capped at 64MB, and virtual / 
locked memory is capped at 256MB, by whoever configured this system. This is 
too low; please try this command:

ulimit -d unlimited -v unlimited -l unlimited

...and then run skipfish in the same session next.

Original comment by lcam...@gmail.com on 2 Jul 2010 at 5:48

• Changed state: Invalid