material-maker icon indicating copy to clipboard operation
material-maker copied to clipboard

Out of application memory on macOS

Open leftbones opened this issue 2 months ago • 5 comments

Material Maker version: 1.4

OS/device including version: macOS Tahoe 26.0

Issue description: While using the program I noticed the memory number in the corner steadily going up, after awhile I got the system popup telling me my laptop was out of application memory and it said Material Maker was using 25GB, it had to be force closed.

Steps to reproduce: Unsure exactly, I only had six very basic nodes in my project as I'm still learning the ropes. About 10 minutes before the memory issues, I had changed the max buffer size from the default (Unlimited) to 2048x2048, since I was noticing some lag.

It may be worth noting that when the "crash" actually happened, I was selecting colors in a colorize node.

leftbones avatar Nov 10 '25 18:11 leftbones

I was just able to replicate the crash within only a few minutes of picking colors in the "colorize rainbow" node or whatever it's called, it only took a few minutes to rocket up to 28GB application memory

leftbones avatar Nov 10 '25 20:11 leftbones

Today I'm using this again and it's currently sitting at 11.5GB memory in the bottom right, I haven't used the colorize rainbow, node, I used the regular colorize node and was able to pick two colors without the memory increasing (although I did it very quickly)

leftbones avatar Nov 11 '25 17:11 leftbones

I figured out how to reproduce this reliably, even in the regular colorize node.

I click the dropdown on the colorize node to open the larger version of the gradient editor thing, then if I either move the sliders around or open the color picker and move the dot around to change the color, the memory increases rapidly

leftbones avatar Nov 11 '25 17:11 leftbones

I can only reproduce this for static materials when it's connected to the material node, memory stays the same if it's just editing the node itself

https://github.com/user-attachments/assets/37aca4e1-cc0f-47e6-8417-f381a3da2e47

non-static

https://github.com/user-attachments/assets/db0a3218-e9e5-467a-97af-665128959f94

probably something to do with buffers

williamchange avatar Nov 12 '25 03:11 williamchange

I got this to happen again today in a new project, no colorize nodes, I was using pretty basic stuff like a shape and a transform repeat and a normal map. It was hooked up to the albedo of the material.

leftbones avatar Nov 12 '25 20:11 leftbones