You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue description:
Trying to move any node results in a crash, verbose logging says segmentation fault. Version 1.3 does not crash on the same system. System is up-to-date. https://youtu.be/rslMrFNIDDs
Steps to reproduce:
Run Material Maker 1.4a2
Try to move a node
If it doesn't crash immediately, do other things in the program and try to move a node again
Program should crash
The text was updated successfully, but these errors were encountered:
UPDATE The power went out so I had to restart my computer. The bug is no longer there which makes me think its because the computer was on for so long. Not sure if you guys still want to pursue this bug because it will affect a very small amount of people. At the same time, no other program crashes like this just from the computer being on for so long.
The program still crashes when trying to move nodes, just not as frequently? As of now, the Static PBR Material node can be moved around. Then, I added another node (node type doesn't matter) and tried to move it. Then the program crashed. After adding a new node, I can still move the Static PBR Material node; it is the added node that crashes the program. So it was not because my computer was on for so long.
It's hard to pinpoint because the cause for crashing doesn't seem consistent. Yesterday moving any node resulted in a crash, now its only the default Static PBR node. The only thing that has changed since then is I restarted my computer.
If any more info is needed, reply and i'll get back to you.
Material Maker version:
Material Maker 1.4a2 Linux
OS/device including version:
Debian 12.9; Desktop B450/ac R2.0; R7 2700X; RX 590;
Issue description:
Trying to move any node results in a crash, verbose logging says segmentation fault. Version 1.3 does not crash on the same system. System is up-to-date. https://youtu.be/rslMrFNIDDs
Steps to reproduce:
The text was updated successfully, but these errors were encountered: