-
Notifications
You must be signed in to change notification settings - Fork 463
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
intermittent fatal erros #61
Comments
Does grunt-sass or node-sass use threads? The backtrace starts and ends with pthread calls but it's not clear where they're coming from. Also, in your node-sass issue you said it happens "roughly once in every 10 runs". That sounds consistent with a race condition to me. What does |
Also, are you actually running LibSass, or just buiding it? (I've tried to make LibSass re-entrant.) |
Hi again, sorry for slow reply, I was away the past few days. I don't believe grunt-sass or node-sass use threads, they're both just very thin javascript wrappers around libsass. Ive not compiled LibSass either, all Im doing is using grunt-sass in my automated grunt build, this then includes node-sass which wraps a built libsass I believe (I'll double check that - havent poked around inside them too much yet). Here's a new trace using 'thread apply all backtrace'.
|
Note the output |
@gregtillbrook Can you provide a copy of the Sass stylesheets that you're trying to compile? Then I can test them myself and try to reproduce the problem -- it could be that there's a null pointer dereference that I haven't caught. |
I cant provide the exact same sass as technically my client owns it and its not mine to share. I'll make a generic sample that reproduces the same problem (bare with me though as this week is looking like a busy one..) How would like me to send it to you? Email or just paste it here? |
A generic sample that reproduces the crash should be fine -- just post it here, if you can. Thanks! |
Sorry about the lack of response. I did at the time try to create a simplified case but without success. Since then Ive moved project and then job so this issue is no longer affecting me - so i'll close this issue. Thanks a lot for all your help! |
Hi, Ive been getting the following errors intermittently when building sass;
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
Not very helpful - but with some help from a issue I raised in node-sass I was able to get the following stack trace;
Does that provide enough info to be of help?
Im running on a Mac - OS X 10.7.5
Im auto building sass with 'grunt watch' using -> grunt-sass which wraps -> node-sass which wraps -> libsass
The text was updated successfully, but these errors were encountered: