art3mis Posted December 10, 2017 Share Posted December 10, 2017 Ok so getting a crash when selecting a new RenderView feature with the latest Redshift plugin of course have submitted a bug report with redshift but the RS logs don't seem to show any errors. In an effort to troubleshoot can anyone look at my Houdini crash log and possibly suggest what the error might be ...possibly driver related? What does 'Caught signal 11' signify? Crash report from jim; Houdini Version 16.5.290 [Linux 2.6.32-573.3.1.el6.x86_64] Uptime 38 seconds Sun Dec 10 14:20:19 2017 Caught signal 11 Quote Traceback from 4918 ThreadId=0x7f7928c43d40 AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so> AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so> signalCallback(UTsignalHandlerArg) <libHoudiniUT.so> UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo*, void*) const <libHoudiniUT.so> UT_Signal::processSignal(int, siginfo*, void*) <libHoudiniUT.so> __funlockfile <libpthread.so.0> XQueryExtension <libX11.so.6> XInitExtension <libX11.so.6> XextAddDisplay <libXext.so.6> glXCreatePbuffer <libGL.so.1> Quote Link to comment Share on other sites More sharing options...
malexander Posted December 10, 2017 Share Posted December 10, 2017 It looks like either the Redshift renderer has used up all available VRAM, or done something to the driver's internal state to mess it up. I'm guessing there's no crash if you create a new Render View without using Redshift (ie, using mantra)? Quote Link to comment Share on other sites More sharing options...
art3mis Posted December 11, 2017 Author Share Posted December 11, 2017 Yep. Hitting the new renderview button is the only thing causing a crash. Problem is they can't seem to reproduce it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.