|
"interference detection" command has bug ???
hi there, forum!!!
i've run into some problems in my sw api experiments...
here's the deal, i've been working in some code of mine to make "intersections detections" and because it has a lot of iterations, sw "bursted" the memory of windows. well it did then, and it still does...
i said to my self "aaaaah, i will just work change the windows definition of swap file and make it bigger and this will solve the problem instantly". wrong. it still burst with the following message at aprox. 2gb of mem usage.
"solidworks is unable to obtain required memory."
"please attempt to free some memory and then press retry, or press cancel to terminate your solidworks session"
then i started to look for the problem, and finally i've encountered the routine that was "consuming" the windows swap file. the problem is (as you can test for yourself by downloading the files below), the sw api command getinterferences keeps getting bigger every iteration. this got me a little bit confused, because of bit that i know of vb language, the variable vints (on my macro) should dump its memory to a "garbage colector", and not keeping geeting bigger.
i've tried this in sw2007_sp3.1 and with sw2009_sp0.0 and they give the same problem ocourrs. i tried also to this "hand made" (without a macro, like a designer!) with the "intersection detection" tool several times on the assembly, and the same thig ocourrs. and it almosts consumes 1mb per calculus.
listen, i'm not saying that sw sucks, i'm sure like everything else it has it limitations, and it keeps getting better with foruns like this, but i'm almost sure that this is a bug of sw and not my unskillfull in vb/sw programming.
can someone gess why this happens??? and can anyone suggest a solution???
come on, lets make sw consume less memory lollololol
best regards to all,
filipe
solidworks
ver. education edition 2007 sp3.1
amd64 3.0 ghz
512mb ddr 400mhz
ati 9550
winxp pro 32bit
portuguese do it better - i do... with this workstation :d
quick |
|