topic Re: Memory issue running Lisp file AutoCAD 2019 in Visual LISP, AutoLISP and General Customization Forum

Memory issue running Lisp file AutoCAD 2019

jcabinnga — Thu, 24 Mar 2022 23:45:41 GMT

Hello,

I've been running a Lisp routine that creates drawings from reading a *.txt file. Inserts a drawing template/executes several commands then w/block to a file/next record repeat. AutoCAD crashes after about 700 drawings made +/- (the *.txt file has about 4300+ records -1 per drawing).

Anyway, I think it is a memory problem? Maybe with my laptop or is there a setting in AutoCAD?

I have Dell Precision 3530 Laptop/Windows 10 Pro 64-bit/32GB RAM. AutoCAD 2019 64bit.

Any help would be appreciated. I'm not sure how to go about changing memory settings on the Laptop or AutoCAD.

Thank you,

Jack

Re: Memory issue running Lisp file AutoCAD 2019

ennujozlagam — Fri, 25 Mar 2022 04:24:01 GMT

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-AutoCAD-is-running-out-of-system-memory.html

https://forums.autodesk.com/t5/autocad-forum/memory-leak-in-autocad-2019/td-p/8272009

Re: Memory issue running Lisp file AutoCAD 2019

jcabinnga — Mon, 04 Apr 2022 14:06:27 GMT

All of the Links you sent concern 32 bit AutoCAD. I have 2019 64 bit AutoCAD.

Thanks.

Re: Memory issue running Lisp file AutoCAD 2019

pendean — Mon, 04 Apr 2022 14:21:15 GMT

1) What LISP? How does it handle file closing after the WBLOCK?
2) How are you running it on 700+ drawings?
3) How often do you need to do this on 700+ drawings?
4) Share with us a screenshot of your ABOUT command pop-up please from the laptop.

Re: Memory issue running Lisp file AutoCAD 2019

jcabinnga — Mon, 04 Apr 2022 15:40:08 GMT

1) (part of lisp)...

;;begin reading file - get first line
(setq cur_rec (read-line fn)) ; reads entire record
(setq cur_pos 1 ctr 0) ; initialize pointer and record counter

(while (/= cur_rec "")

(get_field)
(setq field1 field_value)
(get_field)
(setq field2 field_value)

--------------------------------- (then execute several AutoCAD commands)

;;WBLOCK TO FINAL DRAWING FNAME
(command "wblock" field3 "" "0,0" "all" "")
(COMMAND "UNDO" "BACK" "y")

;(princ "/nFinished Record No /n" (+ ctr 1))

(setq cur_rec (read-line fn)) ; reads entire record
(setq cur_pos 1) ; initialize pointer

) ;end while--end of file

--------------------------------------------

2) I execute the lisp on a "Blank" drawing file. It then reads a "record" of the txt file, inserts a template drawing, executes AutoCAD commands, & then Wblocks all to a file per record, then next record - repeat for 4300 records. AutoCAD crashes at about 700 records.

3) not very often 700+ drawings.

Re: Memory issue running Lisp file AutoCAD 2019

pendean — Mon, 04 Apr 2022 15:52:15 GMT

@jcabinnga Thanks for the screenshot: you are missing all the updates for your 2019 version, the software is currently at the 2019.1.4 level. Get that latest update from your Autodesk Account Page here https://manage.autodesk.com/cep/#products-services/updates

IMPORTANT: Restart your PC afterwards.

HTH

Re: Memory issue running Lisp file AutoCAD 2019

dgorsman — Mon, 04 Apr 2022 21:24:43 GMT

@jcabinnga wrote:

All of the Links you sent concern 32 bit AutoCAD. I have 2019 64 bit AutoCAD.

Thanks.

64 bit or 32 bit, there's still the same problem. AutoCAD (like most programs) isn't built to handle large numbers of sequential drawings without running into memory problems. You'll need to batch process them in blocks, typically 50-100, with additional batch processing to set up subsequent (or even simultaneous) sessions to avoid problems like this. It's not unusual to set up the command console to process a single drawing per session, with multiple sessions running simultaneously up to the effective core count of the processor.

Re: Memory issue running Lisp file AutoCAD 2019

kpblc2000 — Tue, 05 Apr 2022 04:46:23 GMT

Main question is "show your code" 🙂 I've read and created 10000+ dwg-files throuth one AutoCAD session and there was no troubles. Actually I used ObjectDBX mechanism...