@Alfafiles
Okay. I found the issue, fixed the bug and published it here.
Have fun.
P.S.
Please notice us if it works or if you have further problems.

@Alfafiles
I will try it as soon as I'm back home on 28th or 29th.
By the way, did you know that you can publish your world via the load menu?

If you are interested - my saved world. Please note that when loading the world - the correct information will appear on the screens. but the screens freeze and it is just a frozen picture.
The error is not visible in the programmable block menu. You need to restart the program and DO NOT EXIT the block menu, then it is displayed in the right corner.

https://drive.google.com/file/d/1k_m-VHNqnVp-4abkugrYDyb39HKfxOcQ/view?usp=sharing

I got an interesting and even unexpected result.
As a result, I turned off all monitors using "Show Stats", the message "0 LCD panels" literally appeared on the screen of the programmable unit, but still after running the script I see "/" spinning for 1-2 seconds and then STILL this error appears.

I switched the game to English - there is still an error
(I decided that maybe the problem is in the current blocks that are already saved in the world in my language)
I launched your sandbox with examples - no error
I installed different blocks and screens in your sandbox, and called them with long names in Russian - no error.
I ran out of ideas....

@Alfafiles
It is not so much the script, it more the API.
It works "different" in some languages.
As an example: I had to put in exceptions for Chinese and Russian when accessing data from oxygen tanks.
Can you check which of the displays causes the crash?
You could just by change "ShowStats" into "Show Stats" in two of the displays.
Or you could publish the world, where you experience the crash.
It would make the bug hunt much more convenient.
P.S. I will be on the road till 28. or 29. So I won't have access to my gaming rig right now.

I have 3 displays,
1.
ShowStats
Battery ,Addinfo
,Text:Ветрогенераторы
Wind_Turbine, WideBar, NoScrolling, NoNames

2.
ShowStats
Большой контейнер Слитки, SmallBar, NoScrolling, NoNames, Text: Всего:
Большой контейнер Слитки, Weight NoIcons NoScrolling NoNames Filter(+Iron) Text: Железо:
3.
ShowStats
Большой контейнер Руда, SmallBar, NoScrolling, NoNames, Text: Всего:
Большой контейнер Руда, NoIcons NoScrolling NoNames Filter(+Ice) Text: Лёд:

--------------
***Большой контейнер Слитки
***Большой контейнер Руда
(name of large containers for ore and ingots, perhaps this version of the script is allergic to names in another language, although I repeat, the old version works fine.)

@Alfafiles
Can you send me the CustomData field of the display that causes FSD to throw a exception?

I downloaded this literally for the "weight" option, launched this script in my usual survival world, but after a second of work in the programmable block (bottom right, where the inscription "F.S.D. active" is usually) a lot of text appears on the error in the script, I do not understand how to copy it to show you ... If instead of this script I launch the old one (the usual version 37u) it works fine.

https://sp.zhabite.com/sharedfiles/filedetails/?id=3390237800

Well they are convenient for this type of display.
By the way the other two displays use them too.

SemiCircles? Haha, you are probably the first person to use them ever)

Btw, nice in game editor.

Believe it or not.
There are only two triangles used in the top display and those are the tiny arrows at the end of both axis.
The blue body of the graph is made out of 25 semicircles.

So the top one has blue filled with triangles or triangles plus squares, right? That's neat.

I have a script that allows making similar stuff with resize-reposition of everything using mouse drag. I also use in-game sprite drawing script instead of Whips converter or similar. Although I'm lazy to implement data-source part because it's a hell of a scope. Maybe some day we could make your one compatible (send each screen output via IGC to the presenter script, or send each item independently) so user could re-arrange and resize stuff with mouse instead of writing complex configs.

https://www.reddit.com/r/spaceengineers/comments/v2w8xm/databound_animations_orbital_painter_and_wip

That graph is a combination of prebuild sprites and something what I call "in script programming"
Basically you can run a rudimentary program on FSD.
You don't have to modify the FSD Script for displaying the different displays
And the sprite count isn't too high.
30 Sprites for the top display
17 Sprites for the middle display
13 Sprites for the bottom display

Graphs like that scary me with their sprite-count, or did you manage to optimize it somehow?
Do you use pre-built sprite frames and show them based on linear min-max interpolation, or build them in code for each particular view-style?