-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
periodic errors #33
Comments
hm hard to tell from here. can you run with gdb and give us a stack trace? |
hmm - not used gdb yet. Ill have a play this weekend and see what I turn up |
Ah, it hadn't clicked that gdb is a C++ debugger. Is that easy to hook up? I thought the debugged object needs to have been built with debugging enabled? For what its worth I tried debugging with node-inspector but got nothing in the inspector when it died and console output was a little different but not looking any more helpful; node(15428,0x1034fe000) malloc: *** mmap(size=2305843009485295616) failed (error code=12) |
gdb works for c/c++, and will still give decent info even without debugging symbols. node-sass is mostly just a thin wrapper around libsass, which is all c++ code so node-inspector will not output anything useful for us. |
Ive had a play with gbc so lets see if Ive been using it right! I attached to the grunt sass process and when the error occured got this; Program received signal SIGABRT, Aborted. I then tried 'backtrace' and got something that appears like it may be more useful - is it? 0 0x00007fff8a32dce2 in __pthread_kill () |
Gah, just noticed the hashes in the stack trace I pasted auto created references in other issues. Have edited them out. Sorry! |
@gregtillbrook does this issue still persist? Please try with node-sass 0.4.3, which requires node 0.10.x. |
Closing due to lack of response. |
Sorry about the lack of response. Ive long since moved on so no longer an issue for me. Cheers, Greg |
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
Hi there.
Ive been using node-sass as part of grunt-sass (set to auto regenerate with grunts watch task) and have been seeing the following periodic errors.
Error shown;
node(14524,0x1017bb000) malloc: *** mmap(size=1152921504876556288) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
terminate called throwing an exceptionAbort trap: 6
The errors seem to happen randomly, roughly once in every 10 runs. If I build again after an error, everything goes fine.
Any idea what could cause that?
Cheers,
Greg
O.S. = Mac OS X
node-sass v0.2.4 as part of grunt-sass v0.2.4
The text was updated successfully, but these errors were encountered: