A crash can damage your file and file damage can cause a crash so for both reasons, it would be a good idea to run a recover on your database to see if any issues are reported.
You might also create a small test file and try saving as PDF to see if you get the same crash or not. If you do not, this is further evidence that there may be a problem with your file or this layout.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
Apologies for the delayed response...
Still crashes with a smaller subset for pdf.
Recover did not correct problem, and still don't know what exactly the problem is.
I will try to do a new layout and see if that helps. Any other suggestions are most welcome.
Another tidbit: to print directly from the layout works fine (I did that yesterday with no problems whatsoever). It's just when I try to save it as a pdf.