Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: davood.kharmanzar on 2015-10-31, 00:02:56
-
It seems that the memory management after 1.3 RC3 versions is not as good as early versions !? is that true ??
the worst case is in RC5 & RC6 when using IR !! :\ :|
-
Sorry, but such a vague report has no other option as to be moved to resolved. Can you provide at least some evidence? The more info you'll give the more chances that devs will find what's wrong.
-
Sorry, but such a vague report has no other option as to be moved to resolved. Can you provide at least some evidence? The more info you'll give the more chances that devs will find what's wrong.
it's so simple ... Just test with an huge scene ... tons of Objects ... tons of data ... tons of proxies ... tons of textures ... especially with IR ...
-
Duplicate: https://forum.corona-renderer.com/index.php/topic,10010.0.html
-
Ok ... just unchecked the low thread priority @ settings & everything is good !! ;)
-
Ok ... just unchecked the low thread priority @ settings & everything is good !! ;)
This work also for slaves machine in distribute mode?
-
Ok ... just unchecked the low thread priority @ settings & everything is good !! ;)
This work also for slaves machine in distribute mode?
Yep ... this set priority of current render process job for current CPU session ...
That's better if you use deadline or other render managements ...
-
Tested the low thread pryority solution, And it seems that it works.
SCR1- Main machine with 32gb ram
SCR2 - Slave node with 16 Gb of ram
RL - Render log from slave (the interesting part where the magic happens)
And i have 2 sugestions about it.
1 - May be add this solution to FAQ or known bugs section.
2 - Chek in previonus versions what was causing better performance. And i have this absolutley stupid idea that it might have been caused by error mesages.
PS - And it works even better if the Low Memory chekbox in devel settings is cheked.
-
The MEMORY_MANAGEMENT error caused the blue screen and in turn the computer shut itself down to prevent further damage to your computer which in turn caused this error to happen. As the log says "This error could be caused if the system stopped responding, crashed, or lost power unexpectedly" proves that the sole reason of this error was from the MEMORY_MANAGEMENT error and is not the MEMORY_MANAGEMENT error
I am Having MEMORY_MANAGEMENTproblem in my PC.
-
Here’s the mail I got recently for my problem
I FIGURED IT OUT!!! I had the exact same problem where it would crash every time I shutdown/restarted the computer. It was extremely frustrating. And for whatever reason windows 10 wouldn't record and error report and it would stall at 0% when collecting information. I have an acer travelmate 4670 (I know...a little dated...but she runs like a dream with her SSD). Anyways, it wouldn't happen in safe mode but it would still happen if I performed a clean start (shut down extra services in msconfig). So I figured it was a hardware issues as opposed to a software issue which would have resolved with a clean start. So I went to device manager and right-click disabled every extra piece of hardware. Hurray!! It worked! Then I started re-enabling hardware until I found the culprit. For me it turned out to be the conexant 56k modem. I probably could have found a more compatible driver on the internet but I haven't used dial-up for the better part of a decade so I just left it disabled and haven't had a problem since.
Hope this helps!
p.s. Enabling a single piece of hardware and restarting my computer each time was fairly tedious. It dawned on my afterwards that it would have been much faster to enable half the hardware each time.
Ex:
Disabled hardware 1-20...restart...it works!
Enable hardware 1-10...restart...it still works!...not hardware 1-10 giving me trouble
Enable hardware 11-15...restart..problem is back...must be somewhere between 11-15...but hardware 16-20 is good.
That would have been much faster then restarting the computer EACH TIME! What was I thinking using a linear search algorithm!
Or otherwise try this: http://www.deskdecode.com/memory_management-0x0000001a/ (http://www.deskdecode.com/memory_management-0x0000001a/)
-
The MEMORY_MANAGEMENT error caused the blue screen
Corona cannot be the direct source of BSODs. See:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000595168