Jump to content
Ultimaker Community of 3D Printing Experts
lairdb

Cura 2.4.0 app crash at launch

Recommended Posts

Cura 2.4.0, Windows 10.  Event log shows an uncaught c0000005 exception, immediately followed by an uncaught c000041d exception.

May be related to attempting to launch Cura from within an RDP session. (At least, that's the only thing I can think of that's different from the last successful invocation.)

Edited by Guest

Share this post


Link to post
Share on other sites

> May be related to attempting to launch Cura from within an RDP session.

Yes, that is highly likely. Cura requires OpenGL support that is not available over RDP.

 

Well, just crashing is a little abrupt, but that aside: why wouldn't it fall back to the software renderer? Or allow bitmap RDP transmission of the local OpenGL render, as happens if I launch Cura before connecting with RDP? (See screenshot below.)

2017-03-13%2014_59_58-apricot.cloverhurst.local%20-%20Remote%20Desktop%20Connection_1.png

Share this post


Link to post
Share on other sites

Well, just crashing is a little abrupt,

 

No argument there.

 

why wouldn't it fall back to the software renderer?  Or allow bitmap RDP transmission of the local OpenGL render, as happens if I launch Cura before connecting with RDP?

 

It is not like the code contains a line like "if RunningOverRdp: justGiveUpAndCrash()".

Running Cura over RDP is not something that is supported, so it is not tested. There's a limited amount of developer and tester resources at Ultimaker, and they've not chosen (sofar) to put any resources on this usecase.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

Terms of Use Privacy Policy