i am a bit jealous, i never ever saw that on mac…
I spent three hours last night modeling and visualizing, so far I got once crash that happened on the insertion of a chaos cosmos object and I think this is a V-Ray issue. I’ll investigate this more today and will let everyone know.
So far, good job guys!
I just released Rhino WIP 8.0.23251 which has the toolbar tooltip crash fixed, and also should do a much better job reporting crashes to us. If you see crashes without the crash report dialog after today’s WIP, please please please let me know. We’ve been living in a false sense of stability at McNeel because we haven’t been getting the memo that Rhino is crashing.
If I may suggest/request something here.
It will be helpful and reassuring if you consider implementing an auto email reply to us for the crash reports we send.
I probably sent about 10 reports the last week or 2… No one got back to me regarding these, nor were there any replies to post regarding these crashes…
I assumed you guys are overwhelmed with crashes, or the reports never made it to be looked at, or they are simple the same as many other and there was no need to address them specifically…
An auto reply with some details of the reports [time, date, what we wrote in the description… ] will both serve as a reassurance to users that their report made it through, and will help us remember what and how the crash happened in case you guys ask for more info…
As for now, once we sent the report, it’s gone, [without a trace, from our side]
thanks a lot
Akash
Here is another UI crash that just happened, I think this time is related to containers. It is reported as well through the dialog.
[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
[END ERROR]
A Simpler way to reproduce the crash is by switching between UI presets.
Thanks @Japhy
Thanks Tay; we received your crash report and I referenced your video when creating the bug for this.
We agree and are trying to figure out a system where we can do a better job of getting back to you.
Crashed now.
Tried the command View capture to file, instant crash.
[Sent the crash report just now.]
BTW. I can’t really recall a crash without a crash report appearing … Which call to speculate that this [no report popping out] could possibly be a Windows specific bug …?
thanks a lot
Akash
That was a Windows specific issue
We did get your crash. It was Bella renderer related. We’re trying to determine if it is something we can adjust in core Rhino or if Bella needs to change.
checked this out, and if you are referring to the missing bitmap LockBits method, I have confirmed I can use GetPixel instead, as this particular code doesn’t need to be fast, only being used when doing view capture
Yes, this crash looks to be a missing LockBits method on Mac.
4 posts were split to a new topic: Restore Window Layout Crash
Just for reference, System.Drawing.Bitmap.LockBits
should work on Mac when running in Rhino, just not when you are passing a smaller rectangle than the full bitmap, using new Rectangle(0, 0, bmp.Width, bmp.Height)
should work. If you are only getting a few pixels then GetPixel
should work just fine.
Thanks for the suggestion; we can do that. I’ll look into it this week.
Rhino BETA crashed without crash report dialog while hatching:
RhinoDotNetCrash.txt (1.0 KB)
I don’t think that I have ever seen that dialog come up when the Beta crashed… and crashing it does!