Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => Topic started by: dj_buckley on 2024-07-10, 12:14:45
-
I seem to be experiencing a pretty serious memory leak with Corona 12.
I'm trying to pinpoint it exactly at the minute, but it seems to be when I try to use IR for the first time after merging a 3rd party model into my scene.
The process goes something like this
- merge model
- continue working (no problems yet)
- start IR
- memory leak
but
If I save the scene after merging, close max, reopen the scene and start IR then its fine.
But the memory leak is literally causing my computer to lock out and ultimately crash requiring a full restart.
-
had some issues as well, starting IR and getting white VFB screen, CPU 100%, memory getting high. but no rendering visible
google complained about memory lacking (first time i had this, 64GB system btw)
had to kill 3dsmax.exe
-
I'm on 192GB RAM and it just completely locks out my machine, i'm working in a scene that just contains a few boxes really (screenshot attached) and the file is 45MB. But as soon as I press IR after merging a new model in, memory usage in task manager shoots above 150GB and then just keeps climbing.
If I catch it quick enough i can end task in task manager, if not then it's a full PC restart
-
Does it happen after merging literally ANY model, or only some specific model(s)?
If it's specific models only, could you please send at least one of them which triggers the issue at https://support.chaos.com/hc/en-us/requests/new
Thanks in advance!
-
It's happened with two different models so far, one from 3D Sky, the other from Dimensiva.
I've just tried again with one of the models and it didn't happen, so it's not consistent either.
I seem to have a knack for finding inconsistent seemingly random and impossible to pinpoint bugs :)
Edit: Might be something, but previously when it's been happening, I've had multiple instances of Max open. When I tried again just now I only have 1 instance of Max open
-
Have you tried using scripts like Stock Model Fixer, SiNi Forensic and Prune Scene?
I always run these 3 scripts everytime after merging any third party model, as I have experienced weird behaviors in the past with 3rd party models (max file size increasing, unusualy long loading time etc...)
-
Yeh it's none of that, these are models I've used plenty times in the past, i'm literally merging them in from older scenes using Copy/Paste script
-
Same problem here, my 100GB of ram used entirely at random when I launch IR, forced to regularly kill the process and relaunch max.
-
Gentlemen, I have set up support tickets for each one of you.
-
Yeh it's none of that, these are models I've used plenty times in the past, i'm literally merging them in from older scenes using Copy/Paste script
I'd also ask you to check if you have any meshsmooth modifiers on any models in your scene and collapse it. I noticed this with previous version of corona, It happened randomly. in some scenes I had.
-
same issue here
-
I have just created a support ticket #275097 for you.
-
Unfortunately Maru, I think this is another one of those that isn't replicatable on demand. It seems completely and utterly random. I'm also being super cautious since it happened to me and saving my scene file regularly which, for all I know, could be the reason why it's not happened again
-
I had this happen to me yesterday as well.
-
I had this happen to me yesterday as well.
I have just set up a support ticket for you. Please check your mail.
-
I've been experiencing this same issue with several different max files. Very frustrating since I have to crash max.
Currently on Max 2024 with most recent updates.
-
I've been experiencing this same issue with several different max files. Very frustrating since I have to crash max.
Currently on Max 2024 with most recent updates.
You now have a support ticket #284095. Please check your mailbox.
-
I have similar problems on at least three scenes on two different workstations. All with the same set of 3d max 2024 + Plugins. I'm trying Corona 13 at the moment, but nothing has changed. The bad thing is, that these are all confidential data and can not share a lot about these.
On all three scenes rendering behaves the same:
1. Click on render
2. RAM fills up to the maximum (i have 48GB & 64GB, does not matter)
3. VFB shows up and starts rendering
- Workstation 1 does not have any big problems with it and finishes the job
- Workstation 2 locks completely up and needs a hard reset.
-
For several days I've been troubleshooting a typical file in our production environment, and am running out of RAM memory very quickly. My PC has 64GB of RAM and I've even tried the "conserve memory" setting, without success.
I'm coming to the suspicion that Corona v12 (hotfix) has a major memory leak issue.
update: it seems turning caustics OFF has fixed the memory leaks.
-
Please , off displacement than render
Try it
-
For several days I've been troubleshooting a typical file in our production environment, and am running out of RAM memory very quickly. My PC has 64GB of RAM and I've even tried the "conserve memory" setting, without success.
I'm coming to the suspicion that Corona v12 (hotfix) has a major memory leak issue.
update: it seems turning caustics OFF has fixed the memory leaks.
This is now being handled in support ticket #288380.
-
Hi all, out of 7 "memory leak" reports we have received, we were provided with scenes only in 2 of them.
In one case we were not able to reproduce the issue, everything worked fine on our hardware, so it might be system-specific.
In the other one the issue is most likely related to caustics, but we are investigating it.
If you are using caustics in your "memory leak" scenes, please try disabling them and let us know if there is any improvement.
-
Hi all, out of 7 "memory leak" reports we have received, we were provided with scenes only in 2 of them.
In one case we were not able to reproduce the issue, everything worked fine on our hardware, so it might be system-specific.
In the other one the issue is most likely related to caustics, but we are investigating it.
If you are using caustics in your "memory leak" scenes, please try disabling them and let us know if there is any improvement.
Hey Maru
I can't remember if I sent my scene or not, however, I wasn't using caustics. That said, I haven't experienced the same issue since but ... I've not worked on that many new scenes. If it happens again I'll be sure to upload a scene.
-
TY for keeping an eye out and uploading a scene should it crop up again!
I think the main point here is the way the thread on the forum reads, it's as if there is the same thing happening to multiple users, but this is not the case. It certainly appears to be a collection of separate issues (based on as much as we can tell, since we didn't get responses or didn't have scenes to investigate). And it may not even be a "memory leak" - e.g. the caustics example seems to be that it takes more memory in Corona 12 than in an earlier version, but this is not the same as a memory leak (which is the longer a piece of software runs, the more and more memory it consumes as it is not being freed correctly once no longer needed).
So, if this thread is one of the things that has put you off upgrading to Corona 12 because it reads like there is a common, universal, actual memory leak (since I have seen several people say they are not upgrading due to Corona 12 having problems, and I can only assume threads like this one is part of that assessment) - do be sure to asses things in the light of the above and not just on the first impression of reading the thread. So far, no actual memory leak has been found, and one issue of caustics apparently taking more memory than in a previous version is being investigated. Hope this helps!
-
Oh, and rather than leave it as "goes without saying" - those who are experiencing any sort of unexpected memory problems, whether apparently a leak or just needing more memory in 12 than in 11 or more memory in Max 2025 than in 2024, do let us know! I am not saying no-one is running into some sort of issue :) Also, when you do report it, please keep in touch with us when we have questions as part of our investigation, and please send in the scene that causes you problems if at all possible. This is what lets us solve any issues that do exist!
-
Right, I'm uploading a scene this morning. It's only happening with one particular camera (V02_B). Whether it's the same 'memory leak' issue I have no idea but memory shoots up to the point where the PC is unusable.
The scene file is less than 500MB, the assets will add more but it's not a complex scene at all.
I can render other cameras from this scene no problem at all, but this camera seems to giving the same or at least a very similar issue - having said that, it could be a completely different issue, but it's consistent and I can reproduce it every time I render from this camera.
Oddly it works fine with IR, but as soon as I do a production render, the RAM usage shoots right up to the point of crashing.
I keep getting this error window but each time it lists different items under 'heaviest objects'. And if it does list the same item it's always a random GB value.
Circle015 for example is literally an extruded circle so why is it estimating its using 18+GB. There are 8 instances of it, so I have no idea why it's only highlighting that one. It also only has a basic shader on it no high res maps etc.
The Squishmeister Sofa is listed in the screenshot as using 10GB, yesterday it was listed as using 25GB, nothing has changed since.
-
Request #297121
Although now I'm not sure it is the same issue. I have a feeling this was a displacement issue.
-
The issue does really seem to be related to displacement, but we will investigate some more.
-
just a note
also happened to me on C4D using daily v13 w/o any displacement
seems fine w latest v12 HF2
(did mentioned it on discord)
-
The question here is still the same - is this actually a memory leak (ie it starts low and then over time it keeps using more and more memory, suggesting something is taking more memory without freeing up memory it is done with), or just excessive memory usage (ie it gets this high almost as soon as the scene starts rendering)? (and can you send in the offending scene via ticket, would be great to have an example on hand we can test with :) https://support.chaos.com/requests/new )
-
Here is a summary of what we have managed to collect based on the reports from this thread:
#273005
- happened only once, user couldn't reproduce it later
#273007, #275097, #284095
- no response
#292435
- stopped having the problem
#280076
- the issue stopped happening, no further response from the user
#288380
- RAM problem when rendering the scene with caustics – fixed in September
#297121
- issue where an object with detailed displacement is instanced and apparently the multiple instances with displacement are causing a spike in RAM usage – reported to devs as CMAX-1299
If anyone is suspecting a RAM leak / having issues with unexpectedly high RAM usage, please contact us at https://support.chaos.com/hc/en-us/requests/new
Thanks!