Can you edit and save an existing file on your Desktop?
Are you running any third-party system protection tools?
Have you check the rights on the local folder where you are storing files to see if they have changed?
When I edited and saved a file to desktop the same thing happened. It doesn’t happen when it’s saving though. Just when I close the software after I’ve saved. So when I open the file, I didn’t lose anything.
When I then open that file on my desktop and close it again, there’s no crash.
But when I open the file, edit, save and close the software, it crashes again.
I have bitdefender, if that helps in any way?
I’ve never heard of BitDefender and no one else has reported his so I’d try temporarilydisabling it and see if the problem goes away.
I turned bitdefender off. I tried reopening the file on the desktop, edit, save, close. Nothing happened, no crash. I tried it again with bitdefender still being off; open, edit, save, close. “Rhinoceros 6 Developer Build has stopped working”. So it didn’t work…
Rats.
I’m out of ideas.
I assume you are running the current WIP from last week:
rhino_en-us_6.0.16348.09381.exe
6.0.16348.9381, 13/12/2016
Well it’s not an issue since my files stay the same. It wasnt’t happening with the previous WIP so maybe with the bext WIP it solved itself, I’ll keep paying attention to it.
Does this happen with all files? If you start Rhino and just create a file with a single line, do you get the crash with that single line file?
For the last ~3 WIP’s, sometimes after opening or importing a file and closing Rhino, a 0 byte RhinoCrashDump.dmp appears on my Desktop, and Rhino.exe keeps running at its full CPU thread. Since it doesn’t end on its own, I’ll End Process it in Task Manager.
This is 6.0.16348.9381, 12/13/16 on Windows 7 SP1.
It doesn’t happen with all files. I just tried drawing a single line, saving it on my desktop and after closing rhino I got the crash with the single line file. I didn’t have any other rhino windows or versions open.
I also got a mcneel error report window so I’ve send the file in.
If the .dmp file is 0 bytes I’m not sure how we’d figure it out. Siemen, do you get the dialog asking to send in the crash report to Rhino or just the Microsoft crash reporting stuff? If you do get the Rhino dialog, have you sent any crash reports in? What email did you use? That might help us track it down.
Sometimes it asks me to send in the crash report, but I’ve noticed it’s not always. I’ve send the crash reports in two times I think. One time without e-mail address. I’ll send my e-mail address in a message to you.
@tim,
i’ve sent at least one time a related report. On my side the crash happened when rhino was closed without ever opening a file. (despite from the template which is opened automatically).
I also got this crash at least once when i opened the WIP and the “update available” button was clicked (this closes rhino). In the latter case, the update did not start and the error reporting dialog was shown.
c.
Just experienced a case where the crash did become a problem. I made something in Grasshopper and closed the window but forgot to save. I then closed Rhino after saving the Rhino file and usually there’s a window popping up saying you forgot to save your grasshopper definitions. So that window popped up and immediately changed into the crash window so I couldn’t save my grasshopper work anymore.
Anyway, I don’t expect anybody working on this with during the coming days, with Christmas coming up. So Merry Christmas to y’all.
I just installed the latest version of WIP and had the same thing happening. Sorry guys.
No crash report this time though.
the source for this crash has been found at it is worked on a solution. Maybe @tim can shed some light what exactly can be done to prevent the crash at least for the moment.
c.
Great to hear! I don’t necessarily need a way to prevent the crash, just wanted to make sure you guys were aware of it so you could find the problem/solution.
We’re not sure if we have this completely identified, and we for sure don’t have a fix yet (https://mcneel.myjetbrains.com/youtrack/issue/RH-37382). The problem seems to have some relationship to OpenGL pipeline in wireframe views.
Here is what has been a workaround for a few users who are getting crashes on close. Set your display pipeline to Windows for wireframe views. The drawback to the workaround is you get some display wonkiness (https://mcneel.myjetbrains.com/youtrack/issue/RH-37387), but you shouldn’t get the crash.
Tim
Hmm. I think I prefer the crash after I saved and closed my file doing no harm to my files over wonky display issues… But thanks anyway.
I would tend to agree. Setting the display pipeline to “Windows” is NOT recommended at all and I am in general thinking of removing that option from the UI. Windows pipelines are really only supposed to be used for safe mode and for printing functionality.