Rhino WIP Crashing? Do you get the crash report dialog?

Serengeti (Rhino WIP)
13

If we can take that comment literally (no crash report dialog == McNeel doesn’t know about the crash), then I have a suggestion for copies belonging to people who are opt-in on the monitoring feature:

Upon install, create an application data directory for the following.

Upon opening Rhino, create a random uniquely named file and leave it open and write locked. Maybe put something basic like the version+build number in it and flush that to disk.
Also upon opening Rhino, look to see if any of these files exist and are not write-locked (implying that Rhino did not exit in a tidy way whether by crash or terminating the process or etc.). If you find one, call home then delete it and proceed with startup.
Upon closing Rhino or hitting the crash report, delete the file.

14

yes, I see this, I can repeat

This seems a reliable way to crash: Flyout, hover until a tooltip appears, alt-tab to a different app, and alt-tab back to Rhino, it will vanish.
RH-76872 Rhino Crashes With Flyout toolbar + Tooltip

Edit: seems fixed in current build of the day

3 Likes
17

@phcreates and @sach it would be great if you could verify that this crash has actually been fixed on your machine. If you get a chance, could you try our internal build from today and test?

Thanks, we really want to get this one fixed for good.

https://files.mcneel.com/dujour/exe/20230907/rhino_en-us_8.0.23250.06305.exe

18

@stevebaer

I will give it a spin. Thanks.

19

Seems fixed here in the build from today.

1 Like
20

Coming from another Thread as I’m discussing with @Trav about the tooltip crash.
Rhino WIP Repeating Crashes with Isolate objects - Serengeti (Rhino WIP) - McNeel Forum
I just tested the internal building and it seems that the tooltip crash issue is resolved, I’m planning on screen capturing my modeling exercise to report anything new that I might encounter.

Thank you @stevebaer

2 Likes
21

Thank you so much for testing. This is great news.

22

More good news is that we also figured out how to trap and get error reports for crashes like this one. The next build, which we are considering releasing tomorrow, will have the fix for this specific crash, and better crash reporting enabled.

3 Likes
23

Here is a fresh crash report. It seems to be a UI related, I was working on a rendered display mode and I just triggered my heavy toolbar.
RhinoDotNetCrash.txt (6.2 KB)

Attached is my personal popup toolbar for additional diagnosis (probably not needed)
Tay.rui (84.0 KB)

24

13 posts were split to a new topic: Rhino WIP Blue Screen

25

2 posts were merged into an existing topic: SubDDisplayToggle changes display mode to wireframe

30

i am a bit jealous, i never ever saw that on mac…

32
33

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!

1 Like
34

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.

1 Like
35

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

1 Like
36

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]
37

A Simpler way to reproduce the crash is by switching between UI presets.

38

Thanks @Japhy

39

Thanks Tay; we received your crash report and I referenced your video when creating the bug for this.

1 Like