headus 3D tools

dwoje · Posts: 3 Joined: 19 Nov 2008

Greetings,

Wonder if anyone has experienced a memory error. I get a crash anytime i reach 2 gigs...and before you ask i have 8 gigs. I watch the memory build and build as i unwrap and cut and relax. like clockwork with several different objs. it hits 2 gig and crashes.

ive re-installed
restarted
shut off all other programs.

using windows xp
8 gigs of ram
duel quad core processors.

ive been using for months and have no problems.
thanks for any ideas

headus · Posted: Wed Nov 19, 2008 8:22 pm Post subject:

How many polys do your meshes have? I'll do some tests here to see if I can get the same sort of RAM usage you're seeing.

" I watch the memory build and build as i unwrap and cut and relax."

It could be a memory leak. One thing you could try it use the Tmp buttons to save when you see the ram usage getting high, then Load that file back in.

Phil

dwoje · Posts: 3 Joined: 19 Nov 2008

the objs are super simple. i did some more tests and havent found anything new. I did notice the ram would build even if i just pan and rotate around the obj. in Edit or UV mode.

ive been using that work around but it builds to 2 gigs in a matter of min depending on the geo.

it works but its very tedious.

ill try some other stuff today.

headus · Posted: Thu Nov 20, 2008 5:38 pm Post subject:

"ram would build even if i just pan and rotate around the obj"

Yikes, I can see that happening here too! It creeps up by about 4k each step, so would take quite a while to get to 2G, but a leak is a leak. I'll have a look at that today ...

Phil

dwoje · Posts: 3 Joined: 19 Nov 2008

cool, hope youre successful

headus · Posted: Fri Nov 21, 2008 1:34 am Post subject:

I was! I can now load a mesh, spin it around until I get bored, and the RAM usage doesn't budge. It wasn't a leak so much as a pattern of frees and allocs that caused fragmentation. The reason why I haven't noticed before is that I do almost all of my work under Linux ... its malloc is a lot smarter than the same function under Windows.

I cant say if it'll fix your problem though ... with normal usage I couldn't see the fragmentation effect adding much more than a couple of Mb to RAM usage, no-where near the 2Gb that you are getting.

Anyway, I hope to be uploading a new version sometime next week, and this fix will be part of that.

Phil