Cura 2.4.0 app crash at launch

[lairdb 3]

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 March 13, 2017 by Guest

[ahoeben 2,012]

> 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.

[lairdb 3]

> 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.)

[ahoeben 2,012]

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.