I notice OpenGL in the middle of the call stack. So perhaps it crashed doing something about setting up the preview.

Switch to SreeD and see if you can get it to work.

And, no, software cannot examine your video drivers and tell you that you have a buggy driver that is about to crash. It just crashes.

If you're curious, the "Halting Problem" is one of the oldest and most venerated insights in computer science.

http://en.wikipedia.org/wiki/Halting_problem

Basically it says this: For certain very simple programs, it is possible to decide if it stops or runs forever by analyzing it, but in general it is not possible.

Decades later, a branch of computer science has evolved to define a set of rules and if you stay inside those specific rules, it is possible to solve the halting problem. This branch of computer science is called "formal methods" and it's one of my favorite things in the world.

However, people who write video device drivers and 3-D graphic programs can't even tell you what formal methods are, let alone follow them.

http://en.wikipedia.org/wiki/Formal_methods

Quote - Handwritten proofs of correctness need significant time (and thus money) to produce, with limited utility other than assuring correctness. This makes formal methods more likely to be used in fields where it is possible to perform automated proofs using software, or in cases where the cost of a fault is high. Example: in railway engineering and aerospace engineering, undetected errors may cause death, so formal methods are more popular in this field than in other application areas.

It is the generally few deaths associated with CG that make the economics favor buggy software.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)