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 stilldoes...
I said to my self "aaaaah, i will just work change the windowsdefinition of swap file and make it bigger and this will solve theproblem instantly". WRONG. It still burst with the followingmessage at aprox. 2GB of Mem usage.
"SolidWorks is unable to obtain required memory."
"Please attempt to free some memory and then press Retry, or pressCancel to Terminate your SolidWorks session"
Then i started to look for the problem, and finally i'veencountered the routine that was "consuming" the Windows Swap File.The problem is (as you can test for yourself by downloading thefiles below), the SW API command GETINTERFERENCES keeps gettingbigger every iteration. This got me a little bit confused, becauseof bit that i know of VB language, the variable vInts (on my macro)should Dump its memory to a "garbage colector", and not keepinggeeting Bigger.
I've tried this in SW2007_SP3.1 and with SW2009_SP0.0 and they givethe same problem ocourrs. I tried also to this "hand made" (withouta macro, like a designer!) with the "intersection detection" toolseveral times on the assembly, and the same thig ocourrs. And italmosts consumes 1MB per calculus.
Listen, i'm not saying that SW sucks, i'm sure like everything elseit has it limitations, and it keeps getting better with foruns likethis, but i'm almost sure that this is a bug of SW and not myunskillfull in VB/SW programming.
Can someone gess why this happens??? And can anyone suggest asolution???
Come On, lets make SW consume less MEMORY
LOLLOLOLOL
Best regards to all,
Filipe
SolidworksApi macros
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 stilldoes...
I said to my self "aaaaah, i will just work change the windowsdefinition of swap file and make it bigger and this will solve theproblem instantly". WRONG. It still burst with the followingmessage at aprox. 2GB of Mem usage.
"SolidWorks is unable to obtain required memory."
"Please attempt to free some memory and then press Retry, or pressCancel to Terminate your SolidWorks session"
Then i started to look for the problem, and finally i'veencountered the routine that was "consuming" the Windows Swap File.The problem is (as you can test for yourself by downloading thefiles below), the SW API command GETINTERFERENCES keeps gettingbigger every iteration. This got me a little bit confused, becauseof bit that i know of VB language, the variable vInts (on my macro)should Dump its memory to a "garbage colector", and not keepinggeeting Bigger.
I've tried this in SW2007_SP3.1 and with SW2009_SP0.0 and they givethe same problem ocourrs. I tried also to this "hand made" (withouta macro, like a designer!) with the "intersection detection" toolseveral times on the assembly, and the same thig ocourrs. And italmosts consumes 1MB per calculus.
Listen, i'm not saying that SW sucks, i'm sure like everything elseit has it limitations, and it keeps getting better with foruns likethis, but i'm almost sure that this is a bug of SW and not myunskillfull in VB/SW programming.
Can someone gess why this happens??? And can anyone suggest asolution???
Come On, lets make SW consume less MEMORY
LOLLOLOLOLBest regards to all,
Filipe
SolidworksApi macros
