Is there a limit on the length of a component name?

Steve Baumgartner (@slbaumgartner) and I have run into an issue in SU 2022 (not yet tried in earlier versions) where creating a component in Ruby with a long name reliably causes a BugSplat if Outliner is open at the time of creation.

If Outliner is NOT open, the bugsplat doesn’t occur.

Steve speculates that the component name may be exceeding some length limit in Outliner.

Anyone know if there is such a limit, and if so, how many characters are allowed?

If Outliner isn’t open when the plugin is first used to draw the component and name it, no splat occurs, and the full name of the component is visible in both Component Browser and Outliner, so the latter isn’t truncating the name - max length so far tried is 117 characters.

We’ve both submitted bugsplats in the last couple of days, identified by our email addresses.

1 Like

Adding to @john_mcclenahan ‘s info, so far I have only been able to cause this crash on macOS, not on windows.

I’m using the same MacOS and SU version as Steve.

Mac OS 12.2.1, SU 22.0.353. But it was happening in earlier versions of SU 2022 for us both, too.

Win11, SU2022.0.354.
No problrm if, I named (via UI) several groups, component definition, and instances by

this 2481 ch length of string

sajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component namesajkhfsagfjbalsljbjabclajksbcjbljcbdl lkajb lajb ldblak jbkLSBS LAKSJB LAJB SAB LAAKB LA LJJBVVjbbbmnn length component name

Perhaps you can create a post in Developers/RubyAPI category with an example of code causing the issue. Or you can move this to there.

Keep in mind that if you store components with long file names in a library, the file paths will not become too long.

Windows is limited to 260 characters by default.
MacOS can support up to 1024 characters or more.

There’s more going on than just the length of the name. I tried to create a snippet to reproduce the issue with a long name, and it does not crash. For what it’s worth, the most recent for me is Crash #5901.

As I pointed out earlier, so far as I can determine, the crash is Mac only. It doesn’t happen for me on Windows either.

In subsequent testing, we have established that the length of the component name was likely a red herring on Mac. Rather, the bug seems to involve the sequence by which we were building the contents of a Component via the Ruby API somehow triggering a crash if Outliner is open. I’m attempting to create a short script that reliably triggers the crash.

1 Like