#Compositor exited with signal SIGSEGV
6 messages · Page 1 of 1 (latest)
I've only seen SIGKILL, which is due to running out of memory. SIGSEGV is a segment violation.. which might be due to the same reason? not sure -- but in my case, SIGKILL was resolved by increasing the resources available on my lambda\
It sounds like you ran into an error – which one did you get? Please post the full error message, including stacktrace, so that we can help you best.
also, which OS does it happen? which architecture? did you mess with the compositor-* node modules?
It was the issue with my assets. One of the assets didnt load properly from blob storage due to wrong link.