After I update to the last version I cannot export the document to PDF, every time the app crashes. I already delete and reinstall the app but still crashing.
iMac 27″, macOS 10.15
Hi, the file have 30 pages with 5 tables and 10 graphics each. I tried to low the quality on the export to Good instead of Best and it worked.
Well, Juan carlos102.
My attempt succeeded at creating a 115.6 MB PDF.
I'm using 10.15.6, as well.
It seems like some sort of "corruption".
I know you said you deleted Numbers and Reinstalled.
What about Disk Corruption?
Do you have any PDF "extensions", from Adobe or others? (I don't know whether Numbers would access any such, when trying to create a PDF.)
Incidentally, how much RAM do you have? The amount of space Numbers was using seems rather small.
"30 pages with 5 tables and 10 graphics each" doesn't sound all that complex or large, depending upon the nature of the graphics.
Are the "graphics" images that you pasted/imported into Numbers, or are they Charts/Graphs/so-forth?
I haven't had images in my files.
It's too bad that exporting to a PDF at "Best" quality causes a "Crash", but, at least, you have something that kind of works for you, for now.
By the way, does the "Crash" occur if you Print the Numbers file, using similar settings to what you used for the PDF Export? (The one that Crashes.)
The code for Exporting to PDF and Printing should be highly similar!
And how large and/or complex is that file, Juan carlos102?
(Mine is 166 MB, over 140 tables, half over 3000 rows.)
The corruption, such as file system corruption, could easily be the file itself! (That's the other thing in common.)
I still recommend checking the disk (particularly that file) for Corruption.
With 32 GB of RAM, it would appear that if it was going to cause a crash, it should have been on my 8 GB system!
Other than exchanging test files, there doesn't seem to be anything definitive, at this point.
You also didn't address the question of:
Do you have any PDF "extensions", from Adobe or others? (I don't know whether Numbers would access any such, when trying to create a PDF.)
Well officially it's the app. Same crash with same version on different computer. It also crashes on MacBook Pro.
While I've had some "interesting" misbehaviors of Number 10.0 and 10.1—so far (🤞🏻), 10.1 has been more stable, with somewhat fewer issues.
I have a huge spreadsheet, with over a hundred Tables, that has caused me some of my greatest "pain", in Numbers.
I'm currently trying to Export it to PDF, to see if I can reproduce your issue.
So far, it's simply taking a long time! (progress bar shows nothing, yet).
It's not stressing my CPUs at all! (68% idle.)
However, "Memory Pressure" is climbing toward the Red.
(I'm not worried. I've seen far worse, with Number, and my only having 8 GB of RAM.)
I'll get back here, when it crashes or completes!
Here goes the crash log (a bit of course)
I don't think so Halliday, the issue emerges after the update with the same working file. I have 32GB of RAM. I'll try with my MacBookPro and the same file, see what happens.
Numbers 10.1 Crash
