Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

node is sometimes dumping core #6702

Closed
drook opened this issue Dec 14, 2013 · 4 comments
Closed

node is sometimes dumping core #6702

drook opened this issue Dec 14, 2013 · 4 comments
Assignees

Comments

@drook
Copy link

drook commented Dec 14, 2013

OS: Solaris 11.0 x86
gcc version 4.5.2 (GCC)
node: v0.10.22

backtrace:

# gdb /usr/local/node.js/bin/node core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.11"...
Reading symbols from /lib/amd64/libumem.so.1...done.
Loaded symbols for /lib/64/libumem.so.1
Reading symbols from /lib/amd64/libkstat.so.1...done.
Loaded symbols for /lib/64/libkstat.so.1
Reading symbols from /lib/amd64/libsocket.so.1...done.
Loaded symbols for /lib/64/libsocket.so.1
Reading symbols from /lib/amd64/libnsl.so.1...done.
Loaded symbols for /lib/64/libnsl.so.1
Reading symbols from /lib/amd64/libsendfile.so.1...done.
Loaded symbols for /lib/64/libsendfile.so.1
Reading symbols from /usr/lib/amd64/libstdc++.so.6...done.
Loaded symbols for /usr/lib/64/libstdc++.so.6
Reading symbols from /lib/amd64/libm.so.2...done.
Loaded symbols for /lib/64/libm.so.2
Reading symbols from /usr/lib/amd64/libgcc_s.so.1...done.
Loaded symbols for /usr/lib/64/libgcc_s.so.1
Reading symbols from /lib/amd64/libpthread.so.1...
warning: Lowest section in /lib/amd64/libpthread.so.1 is .dynamic at 00000000000000b0
done.
Loaded symbols for /lib/64/libpthread.so.1
Reading symbols from /lib/amd64/libc.so.1...done.
Loaded symbols for /lib/64/libc.so.1
Reading symbols from /usr/local/public/books/underpage/node_modules/clinch/node_modules/xxhash/build/Release/hash.node...done.
Loaded symbols for /usr/local/public/books/underpage/node_modules/clinch/node_modules/xxhash/build/Release/hash.node
Reading symbols from /lib/amd64/ld.so.1...done.
Loaded symbols for /lib/amd64/ld.so.1
Core was generated by `/usr/local/node.js-0.10.22/bin/node /usr/local/public/books/underpage/bin/daemo'.
Program terminated with signal 6, Aborted.
[New process 94097    ]
[New process 159633    ]
[New process 225169    ]
#0  0xfffffd7fff1fb82a in _lwp_kill () from /lib/64/libc.so.1
(gdb) bt
#0  0xfffffd7fff1fb82a in _lwp_kill () from /lib/64/libc.so.1
#1  0xfffffd7fff1f0009 in thr_kill () from /lib/64/libc.so.1
#2  0xfffffd7fff1a1169 in raise () from /lib/64/libc.so.1
#3  0xfffffd7fff177bd2 in abort () from /lib/64/libc.so.1
#4  0x0000000000b03d09 in v8::internal::OS::Abort () at ../deps/v8/src/platform-solaris.cc:196
#5  0x0000000000919f59 in V8_Fatal (file=0xb88f18 "../deps/v8/src/incremental-marking.cc", line=458,
    format=0xb88f04 "CHECK(%s) failed") at ../deps/v8/src/checks.cc:58
#6  0x00000000009b3091 in v8::internal::IncrementalMarking::EnsureMarkingDequeIsCommitted (this=0xdaf8d8)
    at ../deps/v8/src/incremental-marking.cc:458
#7  0x0000000000daf8d8 in ?? ()
#8  0x0000000000000001 in ?? ()
#9  0x00000000009b3171 in v8::internal::IncrementalMarking::StartMarking (this=0xdad010, flag=<value optimized out>)
    at ../deps/v8/src/incremental-marking.cc:526
#10 0x00000000009b3717 in v8::internal::IncrementalMarking::Start (this=0xdaf8d8)
    at ../deps/v8/src/incremental-marking.cc:485
#11 0x0000000000daf8d8 in ?? ()
#12 0x0000000000dad020 in ?? ()
#13 0xfffffd7fffdfcaf0 in ?? ()
#14 0x00000000009716e4 in v8::internal::Heap::CollectGarbage (this=0xfffffd7fffdfc9b0, space=<value optimized out>,
    collector=<value optimized out>, gc_reason=<value optimized out>, collector_reason=<value optimized out>)
    at ../deps/v8/src/heap.cc:644
#15 0x0000000000000000 in ?? ()
(gdb)
@indutny
Copy link
Member

indutny commented Dec 14, 2013

It seems that somehow mmap() is failing to set PROT_ flags on a already existing filled memory chunk... Are you sure that you are not running out of memory?

@ghost ghost assigned indutny Dec 14, 2013
@drook
Copy link
Author

drook commented Dec 14, 2013

This is possible, yes, thank you.
I'll monitor and will confirm or deny.

@indutny
Copy link
Member

indutny commented Jan 16, 2014

Confirming or denying? :)

@drook
Copy link
Author

drook commented Jan 17, 2014

Denying at the moment.

@drook drook closed this as completed Jan 17, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants