Autocad 2018 crash problems.

[charbel.ouba]

So this is what happens. What i usually do is have my files on dropbox and have it linked on  my laptop and work my projects from it. Or just work on my laptop then drag them to dropbox and erase them from my laptop once the project is over.

Lately, every time I try to open a cloud based file. Autocad crashes. From that point on if i try to open a local or a cloud based file the software just stops at the loading bar right after the checking license load. 

If i try to reinstall or repair Autocad, I get an error message saying that acad.exe is running. Problem is autocad isn't open and if try to go to my task manager I don't see it. Plus the task manager gets weird and starts not responding at all.

Restarting the laptop usually fixes the problem, but I find it inconvenient to always have to restart to get working again. 

[rkmcswain]

I would suggest to always work on files that are located locally, on your "C" drive or on a local server. AutoCAD makes use of the 'drawing folder' to create files (.BAK, .DWL, .DWL2) as well as including this location in the search path. If there is anything out of the ordinary that it encounters, a fatal error would not be unexpected. Also check your %temp% folder for an excessive number of files/folders. Keep this folder relatively clean.

[charbel.ouba]

thanks for the fast reply @rkmcswain. I was working right now on a local file and it crashed and the issue occurred again. I'm starting to thing that the issue happens everytime Autocad crashes. 

Do you know what the path to the temp file is ? Maybe clearing some old backups there could help lighten autocad.

[rkmcswain]

charbel.ouba wrote:

Do you know what the path to the temp file is ? Maybe clearing some old backups there could help lighten autocad.

Open Windows Explorer. In the address bar, type in %TEMP% and press enter. What you type in will be calculated and display in the address bar after you press enter.

[john.vellek]

HI @charbel.ouba,

Working on the Cloud means that you are relying on synchronization to happen perfectly. If you can share a file or two I would like to see if they report errors.

[charbel.ouba]

Hi @john.vellek,

So after some test, this crash happens on files that are local as well.

I'll attach the file I tried to open today and caused the crash. Thing is every time I get I crash. It doesn't let me see the details to know exactly what happened.

[john.vellek]

Hi @charbel.ouba,

It appears that you are saving down to 2010 file format.  This perhaps could be the issue if some things in your file are not totally backward compatible.  Please try saving it as a default 2018 format to see if that changes the behavior.

It might also be worth renaming a couple of your layers so they do not contain characters with accent marks.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[charbel.ouba]

Thanks for your answer @john.vellek I'll try updating the layers, thing is I've been using this template since 2010 and never had any issue until now. 

Plus, I always save in 2010 because we usually work with other professionals using sometime 2010 or 2013. It just makes it easier. What would be the alternative to make it easier for me and other professionals to collaborate without having to always duplicate my file to 2010 every time I have to send them a file ?

[john.vellek]

Hi @charbel.ouba,

I prefer to never "dumb down" my files and let the other party do that on their side.  It can be done easily DWG Trueview or a host of third party applications.

Please let me know if this behaves if you save in the current file format.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[rkmcswain]

charbel.ouba wrote:

Plus, I always save in 2010 because we usually work with other professionals using sometime 2010 or 2013. It just makes it easier. What would be the alternative to make it easier for me and other professionals to collaborate without having to always duplicate my file to 2010 every time I have to send them a file ?

There should be no issues saving down to an earlier version. If you create an object in 2018 that did not exist in 2010, then that object should be dumbed down to core cad entities. Sometimes newer objects survive "round-tripping", which means they would get dumbed-down for 2010, but if ever brought back to 2018, they would be available again.

If saving down to 2010 is causing crashing problems, then I'd say this is a bug, since it's clearly available as an option. If it was not meant to be, it shouldn't be available.