jit.ui for js is crashing my computer
Hello! I think this is my first forum topic, even though I've been using Max for years now :)
I'm finally trying to learn to make some visuals and interactive UI in Max and navigating the Jitter side. With the new v8 objects, I felt like it was a perfect timing to do so!
I was following the jit.ui + javascript recent tutorials by Federico on Youtube for developing a 3D game (excellent, by the way!).
Specifically, I have just reached Part 3 (linked below)
All was going great until I started experiencing severe crashes, specially when it came to part 3.
In the previous parts, Max did crash once (in a way that I'm used to see in other personal projects, not a big deal) . But specially when I started including the jit.ui objects (through JavaScript, so actually importing and using the jit_ui_for_js.js functions directly), I've started experiencing hard crashes. My GPU would just stop and trigger a hard reset, sometimes showing the famous 'blue screen' as it did so.
I tried to comment out each element of each component I had included while following the tutorial and it seems that the .set_scale(0.7) method really catalyzed the crash.
These are the steps in which I have consistently reproduced the error many times:
Starting with the codebase exactly as it is by the end of Part 3 of the 3D Tower defense tutorial
enable the jit.world
delete/recreate the [v8 grid_game.js] object
With the patch unlocked, I try to click/interact with one of the buttons inside the group
Computer immediately shuts down or GPU crashes freezing my screen
Reboot my system
Inside
grid_game_JitUI.js, I comment out the linethis.ui_modelsMenu.set_scale(0.7);Also remove the normalization from
set_width(180);andset_height(365);Open Max and the patch again.
Try to click interact with one of the buttons. No immediate crashes.
My machine is not super high-spec, and it is integrated graphics, but I wouldn't expect a few UI buttons to overload it. I have played many 3D games with this machine (Talos Principle 2, for example), not really at full resolution, but low to mid-range performance.
Maybe it is something specific with my hardware? It is an AMD system. specs below:
Processor AMD Ryzen 9 6900HX with Radeon Graphics 3.30 GHz
Installed RAM 32.0 GB (27.7 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 11 Pro
Version 24H2
Installed on 10/03/2025
OS build 26100.3775
Experience Windows Feature Experience Pack 1000.26100.66.0
Max Version 9.0.5 (x64 windows)
EDIT: while I was writing this post, I opened it again so that I could reproduce/re-confirm steps 7-10 above, and the patch was left open for a while. Before posting my screen froze again and I had to restart the computer (So lucky that the browser saved the state and I didn't have to re-write this entire post!).
So although the scale attribute made things worse, it does not seem to be the source of the issue...
Would this indicate some kind of memory leak perhaps? It could also be a typo I made while reproducing the tutorial code?