Thank you for the post.
To attempt to replicate this, on my computer running Windows XP Service Pack 3, I created a new database file called TestPDF.fmp12. I added a single field and added 5 new records.
My program does not crash either from a scripted PDF creation in Windows XP with Adobe or by using the "Save as PDF" option in Preview on Mac OS X.
Are you able to replicate this in a new database file?
If not, running recovery on your file may be a good idea to see if any problems are reported. Even if no problems are found, I'd test the recovered copy to see if it still exhibits the same behavior.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
1. The recovered copy may behave differently even if recover reports "no problems found".
2. Recover does not detect all problems
3. Recover doesn't always fix all problems correctly
4. 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.
If you are able to replicate this behavior outside of the current database file, using a new database file built in FileMaker Pro 12 or one of the starter solutions, please let me know.