LISP causing crashes?

[Commandobill]

Ok, perhaps this is the wrong place to ask, but here we go.

 

I have been creating LISP routines for AutoCAD for 8ish years and I have never experienced an issue with AutoCAD crashes in the past (due to LISP). My "CAD Lead", however, is blaming the LISP routines for the increased amount of crashes at my company.

 

He is terribly misinformed about LISP, but I can't seem to find any articles saying that LISP routines don't affect the performance of AutoCAD, and unfortunately, the director isn't great when it comes to technology and is taking the "guilty until proven innocent" stance.

 

Any ideas on how I can persuade them that it is more likely the crappy video cards we have? Thanks

[Lee Mac]

Keep a log of the crashes.

 

Run a particular machine for a week with the customisations enabled.

 

Run the same machine for a week with no customisations enabled.

 

Compare log results.

[iconeo]

IMO, even if I did, which it probably isn't, a crash or two is completely worth the productivity increase that LISP offers. Else, I'd have my team on LT...

[BIGAL]

The only thing I would point at apart from graphics is total ram if your projects are getting bigger it can some times lead to crashes particualrly if you have images in the dwg as well.

[iconeo]

I would also be keeping an eye out for client/consultant drawings laden with AEC/proxy objects.

[Commandobill]

Keep a log of the crashes.

 

Run a particular machine for a week with the customisations enabled.

 

Run the same machine for a week with no customisations enabled.

 

Compare log results.

 

The funny thing is that my co workers would cry with lisps for a week.

[Commandobill]

The only thing I would point at apart from graphics is total ram if your projects are getting bigger it can some times lead to crashes particualrly if you have images in the dwg as well.

 

We have really good ram, 32g right now. Thanks though.

[iconeo]

One thing you might explain is that generally a LISP will run a set of commands and then it's done. Meaning that unless the crash occurs during the execution of the LISP then it most likely isn't the culprit.

[Tharwat]

Reactors that did not written in a precise manner / method than account for every eventuality for the purpose of program that it is written for, should strongly be a culprit.