Rhino for Mac crashes on typing into Help Menu Search Field

Hi there,
on Yosemite 10.10.1 Rhino 5A629 crashes every time when I start typing letters into the Help Menu Search Field. Precisely I wanted to find out where entry points are on “History” in the menu structure of rhino. Normal behavior in other apps would be to get a pointer to menu entries which match the entered (sub)string. Instead, rhino will always crash right on the first key stroke.

Software versions
Rhinoceros version: 5.0 Wenatchee 2014-12-17 (5A629)
IronPython version: not installed
Language: en (MacOS default)
OS X version: Version 10.10.1 (Build 14B25)

If you need further details on HW or SW to reproduce this case on your system, please let me know.

Cheers.

fwiw, this might be something to do with your exact configuration… seems fine here:

are you sending the crash report to mcneel upon relaunching rhino?


i always thought this was an osx controlled feature instead of something the individual developers have to do but i’m not sure about that.
?

Hi Jeff,
thanks for your speedy reply. Your screenshot reflects exactly what I tried to do – in my case without success.

I have no further insight whether the OS should handle this entirely or the app devs need to care for that, too.

For the crash report: no, I did not send one. I’ll go ahead to figure out if that is an option or not. Since your rhino didn’t crash apparently, I can see a crash report could be useful to have more details.

ususally when rhino crashes, there’s a chance to send a report directly to Mcneel upon relaunching the application.
when you relaunch rhino after this crash, are you not being prompted to send a report?

(i’m not talking about the apple crash report… though i suppose you could send that one too)


you should be getting this upon relaunching rhino after a crash:

yes, I’m aware of these two different crash report schemes.
Rhino prompted me to send a report after the crash, which I declined first. Now, that I’ve looked into that in detail, I’ve send out that report to you. Hope you got it and it turns out to be useful.

one more detail: This crash also happens on a totally new model. So no work needs to be done, no file on disk needs to be created. Just open rhino, create new model, go to help menu and type one single letter into the search field to let the crash happen.

heh… well you didn’t send it to me… i’m just some dude on the internet. :smile:

but yeah, it will go to the correct people who know how to properly analyze these types of problems.


for future reference at this forum–
the McNeel employees have a tag next to their name identifying them as such:

1 Like

Sure.

Thanks for clarification on your role here, Jeff. At first I took it that, due to your kind replies and assistance, that you’d play some sort of active role in bug fixing or development in general on rhino. I didn’t consider whether you’re an employee or not. Anyways, thanks for your help and let’s hope the bug gets fixed soon.

Cheers.

I’m not able to replicate the crash either. More disturbing however, is that I’m not seeing your crash report yet (which, yes, could be very helpful to us to have). @marlin, looks like crash reporting might be out-of-whack again.


We’re very happy to have @jeff_hammond’s help.

1 Like

Hi Dan,
well, Rhino at least threw a large thank you on the screen after submit.
Is it a feasible or reasonable way to put in in here as a private message?

Yes, definitely. The best way would be via e-mail with an attached text file. Please copy/paste the entire contents of the Problem and System Information (the bottom text panel) into a text file and attach it to an e-mail to dan@mcneel.com.

This part…

…just place your cursor in the text area and do a command+A, command+C, then a command+V into TextEdit. Please save, attach and send.

Thanks!

Instead of emailing large things like this, I’d rather put it on our webserver for you to see it with one klick:
http://zdio.de/tmp/rhino_crashdump20150116.txt

If you need further details, pls let me know.

Awesome. Thanks. We’ve got what we need and we’ll take a look.

I’ve looked at the crash reports and this is one of those “shouldn’t happen” type of crashes. I’ve revised the code so the troublesome area is handled differently and this will be in the next WIP release.

Hi there, just wanted to give you feedback on this:
With 5A671 running on my main computer suffering from this bug, I now can successfully type into help menu’s search field without seeing rhino crash. Thanks a lot.
Cheers.