Pages Document Crashes in Mojave (not H.Sierra)

You tell us nothing other than you have a gargantuan Pages document that you are attempting to access on some version of Mojave. This dump would be meaningful to Pages product team engineers, but useless to the fellow users that actually participate here.

You state that this occurs on Mojave. What Mojave? Is it 10.14.0, 10.14.1, 10.14.2, or 10.14.3 beta? Is it Pages v7.2 or Pages v7.3? If you are attempting to run a production version of Pages on a Mojave beta, then the discussion is over as we are not permitted by the terms of these communities, or the Apple beta — to provide support or discussion of beta products in these communities.

The usual fix for a crashing Pages is to press and hold the shift key while launching the application — then open the document. If that does not work, try booting into Safe Boot mode, and try opening your document there. If it does not crash, but does crash again on normal reboot, then there is something in the operating system that is loading (kernel extension, or application process) that is incompatible.

To avoid twenty more questions, I suggest that you install and run EtreCheck to tell us about the hardware, installed, and running software. I would do this while Pages is running with that document open, or immediately before you run it. Post the (privacy information excluded) results of EtreCheck into the Note object (third from right icon) on the bottom bar of this editor.

pages crashes when I try to open a docx document

Details below :

Process: Pages [663]

Path: /Applications/Pages.app/Contents/MacOS/Pages

Identifier: com.apple.iWork.Pages

Version: 6.0.5 (4052)

Build Info: Pages-4052000000000000~1

App Item ID: 409201541

App External ID: 818986804

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Pages [663]

User ID: 501

Date/Time: 2019-01-16 18:13:15.096 +0100

OS Version: Mac OS X 10.14.2 (18C54)

Report Version: 12

Anonymous UUID: E9EB301D-F43A-557B-1094-B029BFA5154F

Time Awake Since Boot: 440 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4

Termination Reason: Namespace SIGNAL, Code 0x4

Terminating Process: exc handler [663]

Application Specific Information:

Crashing on exception: -[NSNib _initWithNibNamed:bundle:options:] could not load the nibName: TMAActivityLogViewController in bundle (null).

Application Specific Backtrace 1:

0 CoreFoundation 0x00007fff32ec0ecd __exceptionPreprocess + 256

1 libobjc.A.dylib 0x00007fff5ef78720 objc_exception_throw + 48

2 CoreFoundation 0x00007fff32ec0cff +[NSException raise:format:] + 201

3 AppKit 0x00007fff304e6630 -[NSNib _initWithNibNamed:bundle:options:] + 643

4 AppKit 0x00007fff304e635d -[NSViewController _nibWithName:bundle:] + 183

5 AppKit 0x00007fff304e5f10 -[NSViewController loadView] + 139

6 AppKit 0x00007fff304e1b60 -[NSViewController _loadViewIfRequired] + 75

7 AppKit 0x00007fff304e1acb -[NSViewController view] + 30

Apple's intention for Pages was the antithesis of Word and InDesign — complicated, corporate applications with a very long learning curve, unfriendly user interface, and expensive. How do you believe that a free application would even compete?

Apple marketing would have you believe that Pages is an end all replacement DTP application, but look at Apple's target market all these years — consumers. Anyone that has used Word, InDesign, or Quark would simply view Pages as a toy that Apple essentially ignores. If you want a DTP tool, take a closer look at the Affinity Publisher product (currently in beta).

No one knows (and Apple isn't telling) the upper limits of Pages document content, or physical size — but wouldn't it be a shaft to reach that after several months of work, and then determine you have to start over in Word, or InDesign to finish. There have been book writers that have posted their anguish here in the past. Not everyone can cost justify an iMac Pro to open large Pages documents.

We are fellow users here, so no idea what is going on with iBooks Author evolution. Another Apple application that gets worse treatment than Pages. Incompatiblity does not appear to worry Apple both presently, or historically.

no I'm new - will create a new topic

Thanks !

MESSAGE TO ZEZO52

Hi zezo,

Are you (1) the originator of this discussion (EdgarRothermich) now posting a reply from a different account, or

(2) did you post here because you have what appears to be a similar issue?

Either way, your post is muddying the waters, rather that helping with the solution.

If the first, please say so, and provide the information Viking requested.

If the second, please monitor the conversation from the sidelines until those details are posted by EdgarRothermich and his issue is investigated (and, we hope, solved).

Regards,

Barry

PS: If I'm reading the report in your post, you are using Pages 6.0.5 (not compatible with macOS Mojave), which may make your issue significantly different from the one being discussed here. Best path might be to repeat you post above as a NEW topic (and include the OS version number and version number of Pages that you are actually using.

macOS: Apple menu > About this Mac

Pages:   Pages menu: About Pages

B.

Pages was never designed to take the place of Word or InDesign, and the size and content of your document is more miracle, than anything else. Although one can hope otherwise, I suspect that you will encounter further growing pains with Pages.