clarkbreyman Posted December 14, 2019 Share Posted December 14, 2019 Working on a very simply model (my first - just a kitchen) in X11 on MBP 13 2018 (16GB ram, Quad i7). I started getting lock ups when using materials and things have progressed to more random lockups opening views and panning. The most recent stack trace looks like this at the bottom: 47 qtrender::CAOpenGLWidget::paintGL() + 169 (CAInterior + 19921801) [0x10befdb89] 47 QMetaObject::activate(QObject*, int, int, void**) + 2320 (QtCore + 2219168) [0x127728ca0] 47 qtrender::LayeredCanvasGL::paintLayers(bool) + 183 (CAInterior + 19950759) [0x10bf04ca7] 47 qtrender::LayeredCanvas::paintLayersCore(bool) + 322 (CAInterior + 19941442) [0x10bf02842] 47 qtrender::CanvasLayer::doPaint(bool) + 76 (CAInterior + 19922860) [0x10befdfac] 47 qtrender::CanvasLayer::paint(qtrender::PaintTarget&) + 55 (CAInterior + 30269943) [0x10c8dc1f7] 47 QMetaObject::activate(QObject*, int, int, void**) + 2320 (QtCore + 2219168) [0x127728ca0] 47 CanvasPaintGLController::paintGL(qtrender::PaintTarget&) + 164 (CAInterior + 7998116) [0x10b39eaa4] 47 CanvasPaintGLController::paintScene(qtrender::PaintTarget&) + 727 (CAInterior + 7998983) [0x10b39ee07] 47 qtrender::PaintTarget::Painter::~Painter() + 31 (CAInterior + 19973631) [0x10bf0a5ff] 47 qtrender::FramebufferPaintTarget::endPaintImpl() + 121 (CAInterior + 19929321) [0x10beff8e9] 47 render_engine::RenderableMesh::drawImpl(render_engine::GpuResourceContext&, unsigned long) const + 1154 (libCARender.dylib + 1362338) [0x11f50e9a2] 47 glDrawArrays_GL3Exec + 254 (GLEngine + 696989) [0x7fff3eff729d] 47 glrIntelRenderVertexArray + 254 (AppleIntelKBLGraphicsGLDriver + 58310) [0x7fff2c5323c6] 47 GenContext::ProgramPipeline() + 16522 (AppleIntelKBLGraphicsGLDriver + 76968) [0x7fff2c536ca8] 47 void updateBindingTable<SGfx3dStateBindingTablePointers>(GenContext*, unsigned int, SGfx3dStateBindingTablePointers&) + 2647 (AppleIntelKBLGraphicsGLDriver + 89325) [0x7fff2c539ced] 43 IOAccelContextAddResource + 8 (IOAccelerator + 9304) [0x7fff58820458] *38 hndl_alltraps + 223 (kernel + 928079) [0xffffff80002e294f] *29 user_trap + 684 (kernel + 2512220) [0xffffff800046555c] *29 exception_triage_thread + 417 (kernel + 1300561) [0xffffff800033d851] *24 exception_deliver + 1295 (kernel + 1299935) [0xffffff800033d5df] *23 mach_exception_raise + 269 (kernel + 1692381) [0xffffff800039d2dd] *16 mach_msg_rpc_from_kernel_body + 268 (kernel + 1320764) [0xffffff800034273c] *16 ipc_kmsg_send + 309 (kernel + 1148453) [0xffffff8000318625] *13 ipc_kobject_server + 568 (kernel + 1317272) [0xffffff8000341998] *13 ??? (kernel + 1693962) [0xffffff800039d90a] *7 catch_mach_exception_raise + 103 (kernel + 1614855) [0xffffff800038a407] *3 handle_ux_exception + 387 (kernel + 7494691) [0xffffff8000925c23] *2 IOLockLock + 33 (kernel + 2480657) [0xffffff800045da11] Kitchen1213B.plan Link to comment Share on other sites More sharing options...
glennw Posted December 14, 2019 Share Posted December 14, 2019 Doesn't seem to be any problems here. Link to comment Share on other sites More sharing options...
Electromen Posted December 14, 2019 Share Posted December 14, 2019 I opened it and viewed it in 3D from several angle, spinning it around. No Problems. Link to comment Share on other sites More sharing options...
clarkbreyman Posted December 14, 2019 Author Share Posted December 14, 2019 @glennw @Electromen - what are your machine specs? Catalina? Macbook 13 2018? Thanks in advance Link to comment Share on other sites More sharing options...
glennw Posted December 14, 2019 Share Posted December 14, 2019 2017 iMac running Catalina. Link to comment Share on other sites More sharing options...
Electromen Posted December 15, 2019 Share Posted December 15, 2019 2017 Mac Pro, Catalina 10.15.2, 3.5GHz 6 Core, 16 GB RAM, Dual AMD FirePro D500 video cards with 3GB each Link to comment Share on other sites More sharing options...
clarkbreyman Posted December 15, 2019 Author Share Posted December 15, 2019 Sound like biggest difference is graphics card. 2017 imac is Radeon. I'm on "Intel Iris Plus Graphics 655 1536 MB". Stack trace looks like an unhandled exception leading to a hang. Link to comment Share on other sites More sharing options...
Dermot Posted December 16, 2019 Share Posted December 16, 2019 It looks like the problem is happening on a very low level (probably in the video card drivers). Check out this help article and if that doesn't help, you may want to contact our technical support team: https://www.chiefarchitect.com/support/article/KB-00106/troubleshooting-3d-camera-view-display-problems-in-chief-architect.html Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now