SW2000 SP6 Causing a Memory Leak

[SBaugh]

Hello,

We have two machines here that are running SW2000 and they both seem to be suffering from a possible memory leak. They run a custom VB program and then SW. If SW doesn't close the memory is not returning to windows and if we have the program close SW the memory is still not going back to windows.

Any suggestions on a good fix??

SW2000 SP6
Win NT SP6
800 CPU & 700 CPU
Oxygen VX-1 and a cheap video card on the other
one is running 386 RAM and the other is running 196 RAM

Thanks,
Scott Baugh, CSWP
George Koch Sons, LLC
Evansville, IN
812-465-9574
sjb@kochllc.com

 

[dsi]

You should download SP10 for SW 2000. If you have the maintenance package, SW 2001 should be available to you.

Could you also provide more detail on the VB application and what it has to do with SolidWorks? I automate SolidWorks with VB6 and have not had any problems. My VB applications start SolidWorks and automatically create models, assemblies and drawings. I also have SolidWorks macros set up to run custom VB utilities. I have not had a problem there either. A little more info may provide some insight into your problem. DimensionalSolutions@Core.com
While I welcome e-mail messages, please post all thread activity in these forums for the benefit of all members.

 

[SBaugh]

Hello,

I don't know the real in-depth portion of this program, but I do know just the basics of it.

The VB Application is for making 3D models, Assemblies, & Drawings of our Products. It uses MS Access as well to develop these products. It is completely automated without hardly any user intervention. That's about the most I know what the program does.

We didn't write the program, but we have a VB programmer that debugged it for almost a year. He has had good results till this mishap happened. This is being used as a partial test and production application right now.

One of the users that is using it continues to either BSOD or Dr. Watson out. We believe he is running out of memory (192Mb). But there are others seeing this with more memory (384Mb)

We have upgraded to SP10 without any noticeable results. They do not plan to use SW2001 for at least 3 months from now. So that’s out.

Hope this gives some more clues to why, (probably not, but its wishful thinking)

Thanks,
Scott Baugh, CSWP
sjb@kochllc.com

 

[dsi]

If this is happening while your VB application is running, there is, most likely, a programming problem. I write programs that do exactly the same thing. Although I have not hit the BSOD, I have encountered Dr. Watson errors in the debugging stage of my applications. This could be due to a lack of error handling or a hundred other reasons. If the programmer is still with you, have them check all of the objects and such, making sure that they are cleared from memory. The SolidWorks API is also changed from time to time, so certain functions will need to be updated in your application. My guess is that the VB program is calling an old API function that has been updated in SolidWorks.

Unfortunately, this does not solve your problem, does it? Worse yet, there are not too many programmers that write applications for SolidWorks. Without actually having the program, I can not be of much help debugging it.
DimensionalSolutions@Core.com
While I welcome e-mail messages, please post all thread activity in these forums for the benefit of all members.