Possible Bug: Max 5.1 memory leak?

[Marsel Khadiyev]

I'll give it a try overnight ! :)

Even so I wouldn't be surprized, as the same behaviour happens with almost all programs. Thats Windows for you !

The important thing is that you can always make a fresh boot.

[halo]

Possible Bug: Max 5.1 :scream:

probably worth waiting for 6, seeing as discreet wont be updating max 5.1 anymore...

[TheWriter]

Since 5 was a bag of bugs, what makes you think we should trust Discreet on 6? You don't always get what you pay for.

[halo]

the point i was trying to make is that theres no point in doing a bug report for a redundant program as even if the bug was acknowledged:

a) it may not be in max 6
b) a patch wont be made for 5 now 6 has been announced

[Dave Black]

And my point, was that is noone posts a report, we may actaully see it back in R6. I am just trying to closeup as many holes in the program while we have a chance. Yes, R5 is not getting patched, but I can't think of a better time to check this sort of thing out, than before a major release.

-3DZ

:D

[halo]

go for it can't do any harm, i just think its worth waiting till 6

btw, this doesnt happen on any of my machines win2k or xp....bad drivers perhaps?

[Dave Black]

Great, thanks halo.

Drivers or golden. It's going to take some time to scientifically figure out exactly what steps causes this leak.

Thanks for checking!

-3DZ

:D

[visualboo]

Actually, I think it's a windows thing.

Try this:
Leave a couple programs open (photoshop, IE, outlook... whatever) and go to bed. Wake up and get to work. See how it takes a while to get back up to speed. I just think that windows is optimizing ALL it's resources for system tasks because it's idle. I think that's a preference too. But anyways, after a little bit it's back and going fast again becuase it starts allocating sys resources to working apps.

[edit] whoops, I see Marsel kinda said that already. :thumbsup:

[Dave Black]

But Max remains using 500+ MBs of memory even after an hour or so of use. Only until it's restarted does it snap back to it's normal memory mode.

You guys are quite possibly correct about it being a windows issue, but I'd personally like to rule out Max as it's the only program that does this.

-3DZ

:D

[visualboo]

hmmm... yeah.

I'll try it with Maya after work today and see what it did overnight.

[gaggle]

Eh, this seems worth checking out. I'll keep MAX open overnight then. Though, should it happen with a fresh MAX that just sits there all through the night?.. that's all I can offer at this time I'm afraid.. don't have eight hours devotable to MAX :).

I'll let Maya sit there as well and see if any of them grows during the night.

[Dave Black]

Hey, I really apprieceate it , guys!

I'm going to try being scientific about it. I'll try it with different states, ie, used all day but not restarted, simply restarted and left standing, etc.

I'm also tracing though my plugins to see if theres any culprit there. Not using a plugin renderer, though, and only really using a few basic ones.

Anywho, thanks again, guys! It could just be my dell systems at work...

-3DZ

:D

[opus13]

i tried it last night, and got slightly different results

max was using an additional 15mb, and photoshop was an additional 162!

its got to be a individual system flaw. ive noted that this has happened with various programs in the past, but never with any relaible results.

[gaggle]

Using Win2k SP3, MAX (R5.1) went from 16,384 k, to 17,916 k useage. Not a whole lot.. though I can't explain why it would go up at all.. Maya didn't, so..

Photoshop went from 50,612 k to 61,700 k, so there's a bit of oddness there too I suppose. Of the remaining.. 37 processes, only one or two of them changed during the night, everything else has remained completly static.

A question to those with the leaking MAX's, could it be possible that it's autosaving or something? Or doing something else on a regular basis.. it'd still be a memoryleak of some sort, just.. pondering on explanations.

3DZ, lemme know if there are more tests that'd be useful to run.

[Marsel Khadiyev]

My guess is, like gaggle said, that its checking constantly for changes in the scene and updating its theHold (undo/redo) structure.

I still don't really think this is a big issue. It is always a good practice to restart max before doing any work.

[LFShade]

I still don't really think this is a big issue. It is always a good practice to restart max before doing any work.
..but then again, wouldn't such a slow leak be undesirable during a marathon render? I haven't personally been able to test for the condition, but if it's true then I would expect it to be causing problems for anyone rendering overnight.

RH

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.