This is very odd. I attach a drawing that is much simpler than the one I first had the issue with. Because it experienced exactly the same problem, I assumed it must be universal. However, this morning I went simpler still and drew a rectangle in SU, sent it to LO and then tried changing the rendering. No problem. So I reloaded the attached drawing and tried the same thing. Immediate crash as before. It suggests there is something wrong with certain files, except that @DaveR was able to change rendering of my original file OK.
Does it help if I post the report that was generated after a crash or is that a dangerous thing to do in a public forum?
John, this is very peculiar. Even when downloaded as you suggest, it causes LO to crash. However, I have just drawn something reasonably involved and that allows me to change rendering fine. There must be something about the specific drawings that is causing it but I cannot think what.
Galv planter does have a component downloaded from the Warehouse, although I edited it. I would have to check with the other drawing but it is certainly possible. Am I getting the impression that downloaded components are often suspect? I think I have seen you post that you always make your own!
@DaveR I copied the component to a new SU file and then transferred that to a new LO file to see if that would cause a crash. It doesnāt. Does that mean the component is āsafeā? Here it is:
Several years ago a friend of mine was getting frequent LO crashes on his Mac which we traced to components heād gotten from the Warehouse. Deleting and purging them from the SKP file solved the crashing. We did find that importing the components into a separate file first and doing a bunch of cleanup before adding to his project helped prevent the crashes.
I have tried various things to see if I can isolate the source of the problem. I havenāt had any success. The issue seems quite random. Drawings with or without third party components can suffer. Since no one else seems to be able to reproduce the problem, it suggest it is not actually to do with the file itself. Perhaps to do with my hardware setup and SU/LO 2018?
I did report the problem to HQ but they seemed to think it was all about freezing or lag. Not sure why. Maybe I didnāt make the issue clear enough?
At the moment your computer is the only one crashing in this way - weāre trying to determine if this is something that we can fix on our end, or if itās a problem with the specific video card & driver on your machine.
Same problem with my computer. Layout 2018 crashing constantly (size of file120 mb)ā¦ as reach 100% in CPU. But at same time computer CPU idle 90%ā¦ I have MacPro
In 2017 it works, crashes but you can work.
Actually Lay out not crashing its just (Not Responding) and if I wait 1-2 min it can return to normal state.
Simon, you are not alone - I am experiencing similar issues: bug splats and ānot respondingā in Layout 2018. I will post my details in another thread so as to not confuse my issues with yours, but the workaround thatās working for me is to save as 2017 version.
Have you submitted a bugsplat report with your contact information on it? I donāt see one, but if we can find a crash report from you it will help with diagnosis. Itās unlikely (but possible) that youāre seeing the same issue.
I am not sure your issue is quite the same. I donāt get bugsplats or not responding. What I get is immediate crashes which bypass the whole bugsplat reporting procedure. Sometimes it is just LO that crashes but sometimes it crashes the whole computer. It seems to be random (some files affected but not others) but the source of the crash is always the same - changing rendering from the default raster to hybrid or vector.
I did try what you suggested about saving in 2017 format and opening in LO 2017 but the same thing happened. So it must be something about the way LO handles files leaving an inbuilt problem. My only totally failsafe option is to revert to SU and LO 2017 altogether. I really hope I donāt have to do that!
I am surprised that I am (so far) the only one with this very specific issue as there must be a lot of people out there running 2018 on a Mac just like mine.
