Prepressforums.com

jason · #1 (**permalink**) 03-03-2005, 08:49 AM

The setup:
G4
Dual 1.42 GHz
512 MB RAM
OSX 10.2.8
InDesign CS

The problem:
When printing some jobs from IDCS I get the "application has unexpectedly quit" dialogue box. This usually happens to jobs that have lots of transparencies that need flattened or that have a vector drawing with thousands of nodes.

The Log reports:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000004

The Process viewer reports while job is printing:
%CPU 100.5 (highest reading)
%Memory 35% (highest reading)

The solution:
Do I just need more RAM??

Maybe 1G??

How much RAM is everyone else running??

Or is it just something else and I'm just stupid??

Thanks
Jason

shonisko · #2 (**permalink**) 03-03-2005, 08:52 AM

Just shooting from the hip but on one work station in our department you must have fonts on like helvetica and times or it crashes try that for the fun of it.

geozinger · #3 (**permalink**) 03-03-2005, 09:37 AM

I run into something similar on occasion. Usually when this starts to happen, I just re-boot and it's fine.

I have an agreement with the owner here, that if we buy Mac workstations, we max out the RAM. It pays for itself in the long run. As a result, our 2 year old mirror door G4's have 2GB RAM in them.

I would suggest possibly upgrading to Panther. It seemed to me after I upgraded, the same apps seemed to run better. But that's just my experience.

I would also suggest repairing your permissions every so often. That seems to keep the Mac running smoothly. :wink:

jason · #4 (**permalink**) 03-04-2005, 06:10 AM

Update:

I do have Times & Helvetica loaded.

Upgraded to 10.3.8 and it still happens.

Searched the internet & apple website without finding much help.

I guess I'll just get some more RAM, don't know what else to try.

Thanks
Jason

MarkDouma · #5 (**permalink**) 03-05-2005, 10:53 AM

Quote:

Originally Posted by jason

Upgraded to 10.3.8 and it still happens.

Ahh, if you have OS X 10.3.x, could you post the whole crash log? I'll take a look at it for you. OS X 10.2.x crash logs weren't all that helpful, but OS X 10.3.x crash logs contain a lot more information that could help pinpoint what's causing the crash.

The following would be the amount I need:

Code:

**********

Host Name:      mdouma46.local
Date/Time:      2005-01-21 13:46:13 -0500
OS Version:     10.3.7 (Build 7S215)
Report Version: 2

Command: InDesign CS
Path:    /Applications/Adobe/Adobe InDesign CS/Adobe InDesign CS.app/Contents/MacOS/InDesign CS
Version: CS 3.0.1 (3010)
PID:     2471
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x0cb82268

Thread 0 Crashed:
0   Image                          	0x0a43beb8 0xa40e000 + 0x2deb8
1   Image                          	0x0a436c4c 0xa40e000 + 0x28c4c
2   Image                          	0x0a45bcd4 0xa40e000 + 0x4dcd4
3   PublicLib                      	0x0061066c 0x487000 + 0x18966c
4   com.apple.NavigationServices   	0x919dd1ec InvokeNavPreviewUPP + 0x18
5   com.apple.NavigationServices   	0x91a03f4c TNavClient::Preview(NavCBRec*) const + 0x30
6   com.apple.NavigationServices   	0x919ec5a8 TBrowseDialog::NodeBrowserControlDrawPreview(TNodeBrowserControl&, TNavNode&, TRect&) + 0x214
7   com.apple.NavigationServices   	0x919fb1d8 TNodeBrowserControl::DrawItem(TNavNode&, unsigned long, unsigned long, Rect const*, short, unsigned char) + 0x6c
8   com.apple.NavigationServices   	0x919f9ebc TNodeBrowserControl::DrawItemDispatch(OpaqueControlRef*, unsigned long, unsigned long, unsigned long, Rect const*, short, unsigned char) + 0x64
9   com.apple.HIToolbox            	0x928bce50 TBrowser::Draw(unsigned long, unsigned long, unsigned long, Rect const&, short, bool) const + 0x34

-- snip --

121 AppFramework                   	0x06454860 0x6447000 + 0xd860
122 AppFramework                   	0x0647adec 0x6447000 + 0x33dec
123 InDesign CS                    	0x000b0d24 0xb0000 + 0xd24

Thread 1:
0   libSystem.B.dylib              	0x9000b20c select + 0xc
1   com.apple.CoreFoundation       	0x90196b10 __CFSocketManager + 0x1fc
2   libSystem.B.dylib              	0x900246e8 _pthread_body + 0x28

Thread 2:
0   libSystem.B.dylib              	0x90018be8 semaphore_timedwait_signal_trap + 0x8
1   libSystem.B.dylib              	0x9000e788 _pthread_cond_wait + 0x268
2   ...ple.CoreServices.CarbonCore 	0x90295ca8 MPWaitOnQueue + 0xe0
3   com.apple.DesktopServices      	0x90918f44 TNodeSyncTask::SyncTaskProc(void*) + 0x70
4   ...ple.CoreServices.CarbonCore 	0x902c6d88 PrivateMPEntryPoint + 0x4c
5   libSystem.B.dylib              	0x900246e8 _pthread_body + 0x28

PPC Thread State:
  srr0: 0x0a43beb8 srr1: 0x0200f030                vrsave: 0x00000000
    cr: 0x44024444  xer: 0x00000004   lr: 0x0a43c30c  ctr: 0x0a43be80
    r0: 0x000000ff   r1: 0xbfffadd0   r2: 0x0a310000   r3: 0x0ed8fdd8
    r4: 0x0f023e00   r5: 0x0cb82268   r6: 0x00000000   r7: 0x0f023e01
    r8: 0x00000012   r9: 0x000000b5  r10: 0x00000002  r11: 0x0ed81ee4
   r12: 0x0a30a768  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
   r16: 0x00000000  r17: 0x00000000  r18: 0x024aeb70  r19: 0x0000000c
   r20: 0x01d78218  r21: 0x00000001  r22: 0x00000000  r23: 0x000640b8
   r24: 0x0000000a  r25: 0x0ed8fdd8  r26: 0xbfffaea0  r27: 0x00000001
   r28: 0x00000002  r29: 0x0000021f  r30: 0x0cb82268  r31: 0x00000001

(Don't need to put in the "Binary Images Description" which is really (really) long.

Oh, this one above is from this crashing problem with InDesign which looks to be a genuine bug.

Hope this helps....

jason · #6 (**permalink**) 03-07-2005, 05:59 AM

I just installed 10.3.8 on Friday, but it did not take long to get the same kernal panic in Quark 6.5 which I am posting. I can post a log from IDCS when I get one if needed.

Thanks
Jason

http://www.prepressforums.com/module..._folders/jason

MarkDouma · #7 (**permalink**) 03-07-2005, 06:51 AM

Quote:

Originally Posted by jason

I just installed 10.3.8 on Friday, but it did not take long to get the same kernal panic in Quark 6.5 which I am posting. I can post a log from IDCS when I get one if needed.

Okay, just to clarify, what you had there wasn't a full-blown kernel panic, just an application that crashed. I wonder if you were referring to the "KERN_PROTECTION_FAILURE"? ;-)

The kernel is like the very first process that starts on your Mac, and oversees the operation of all other processes (or applications). In other words, all other processes or applications run on top of the kernel. When a regular application or process crashes, your Mac is usually okay, since there are still processes running underneath it so that you don't have a total system failure. But, the kernel, being at the very lowest level, doesn't have anyone else to help it, and if it crashes, it's called a panic, and there's no way to recover from that except by restarting. 8O

Anyhow, with the QuarkXPress crash that you had. In looking at the stack trace on the first thread (Thread 0) that crashed, it looks like you had chosen the "Save As..." (or some sort of Save command) command from the File menu. Quark then opened the save dialog, where you clicked a few times (maybe changed from column view to list view?) and then it crashed while trying to determine the number of items that were inside a certain folder.

So, are you having crashes in other applications in the Navigation Services dialogs (Open and Save panels)? In the case of Quark, you might try disabling the "com.quark.QuarkXPress.plist" preference file that will be in your /Users/~/Library/Preferences/ folder. That holds some information about the arrangement, size, location, etc. of your open and save dialogs (and thankfully, nothing else).

Otherwise, what type of install did you do of OS X 10.3.8 from Jaguar? An Upgrade install, Archive and Install, etc.?

Yeah, post the InDesign one if you can.

Hope this helps....