Jump to content

Many problems with new Mac Pro

webdeck

By webdeck
September 23, 2006 in Retrospect 6: Desktop, Workgroup and Server for Mac OS X

Share

Recommended Posts

webdeck

Newbie

webdeck

Posted September 23, 2006

- Report
- Share

Posted September 23, 2006

I upgraded my G5 to a Mac Pro and I am having numerous issues with Retrospect. My system configuration is:

Mac Pro 3.0GHz

2 GB RAM

ATTO UL5D SCSI Adapter

Exabyte VXA-2 1x7 Autoloader

Mac OS X 10.4.7 Client

Retrospect Server 6.1.126

Retrospect Driver Update 6.1.7.101

Issues:

- First launch of Retrospect after a reboot, Retrospect does not recognize the tape drive, but it does recognize the tape library. Quitting and relaunching Retrospect seems to fix the issue.

- Retrospect frequently hangs and stops responding to its UI.

- Retrospect unexpectedly quits during backups without issuing any errors that I can find.

- Retrospect sometimes refuses to launch at all, again giving no errors (app launches, authenticates, relaunches, and then exits before UI appears.)

I have 5 nightly backup scripts that run daily, 2 to tape, and 3 to disk. I also have a backup server to tape for two network clients that backup once per day.

This configuration was rock solid on the G5, but is completely unstable on the Mac Pro. Please advise.

Thanks,

-Mike

Quote

Link to comment

Share on other sites

webdeck

Newbie

webdeck

Posted September 23, 2006

Author

- Report
- Share

Posted September 23, 2006

Update: I can reproducibly make it crash by running one of my disk-to-disk backup scripts. The console log contains the following error when this happens (all of these errors were from a single crash):

Code:

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=4247359488) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=3892318208) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=2244104192) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

LaunchCFMApp(24474,0xb8303e00) malloc: *** vm_allocate(size=2244104192) failed (error code=3)

LaunchCFMApp(24474,0xb8303e00) malloc: *** error: can't allocate region

LaunchCFMApp(24474,0xb8303e00) malloc: *** set a breakpoint in szone_error to debug

Quote

Link to comment

Share on other sites

jimtaylor61

Newbie

jimtaylor61

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

I too (approx. 3 weeks ago) upgraded from G4 desktop to Mac Pro.

Mac Pro

10.4.7 and latest updates (except Mac Pro EFI Firmware Update) - can't get that one to install properly

2 external Maxtor Firewire drives; one of which is target for backup

Have similar problem on Mac Pro that I had on the G4. Retrospect 6.5 set to run backup during the night. Upon waking up Mac Pro in morning, Retrospect then 'activates' and starts the backup process. When this first happened, (even on the G4), I assumed it had something to do with the screen saver, so I set it to 'Never'. After that, still have same problem.

Any thoughts or advice on how to make software do what is intended?

Thanks

Jim Taylor

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Retrospect has been acting incredibly strangely on my Mac Pro running 10.4.7 (not Server). When I first installed it and set it up (I copied the /Library/Preferences/Retrospect folder from my old G5 to the Pro, as detailed in the manual for moving to a new computer, and updated to the latest version of Retrospect), it seemed to work fine. Then after a restart it failed to automatically run the backups. I found a blurb in the knowledge base that said that was a known bug. Then when ever I'd launch Retrospect, it would sometimes crash LaunchRetro or LaunchRetroHlper right after entering my password (I've always had the "Always require password" turned on). Now it *always* crashed after entering my password. So I can't even do a manual backup! This is most annoying.

Any ideas?

Quote

Link to comment

Share on other sites

webdeck

Newbie

webdeck

Posted September 25, 2006

Author

- Report
- Share

Posted September 25, 2006

I've had the same problem with crashing after entering the password (when it gets into this state, it asks for the password even though I have "Always require password" turned off.) I think it is a symptom of Rosetta getting messed up. I'm able to fix it by running this command in the Terminal:

sudo killall translated

That forces the Rosetta translation engine to restart, which should get you working again until the next time Retrospect gets it into a funky state again...

Unfortunately, Retrospect on the Mac Pro appears to be fairly unstable; much different from the rock-solid Retrospect I'm used to using on the G4/G5.

-Mike

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

Have similar problem on Mac Pro that I had on the G4

And yet you post to a thread titled "Many problems with new Mac Pro?" Curious.

> Upon waking up Mac Pro in morning, Retrospect then 'activates' and starts the backup process

Retrospect has never been able to wake a sleeping Macintosh.

When the program frst shipped for OS X, there was no Apple API to allow _any_ program to do that. There is an API available now, but Retrospect has not integrated it into the product.

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

I found a blurb in the knowledge base that said...

Please post the KB article number when you reference something like this.

Dave

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

Unfortunately, Retrospect on the Mac Pro appears to be fairly unstable; much different from the rock-solid Retrospect I'm used to using on the G4/G5.

Considering that it's a different CPU then what Retrospect 6.1 was tested and qualified to work with, and a different version of Mac OS X then what Retrospect 6.1 was tested and qualified to work with, it's not unreasonable to observe problems.

It's actually pretty amazing that Retrospect works at all with Intel based Macs. If there turn out to be different issues with Woodcrest (and the version of OS X that those machine use) then there are with Core Duo (and/or Core2 Duo), that wouldn't surprise me.

Dave

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

Please post the KB article number when you reference something like this.

Dave

It's not in an Apple KB article, but in Dantz's (EMC's, whatever it is now) own Knowledge Base, titled "TITLE: EMC Dantz Retrospect and Mac OS X Tiger Compatibility". Here's the relevant line:

Quote:

Retrospect will not automatically launch after a restart on Mac OS X Tiger

For security reasons, Mac OS X Tiger requires that permissions for Startup Items have more limited UNIX permissions than previous versions of Mac OS X. Prior versions of Retrospect's RetroRun launch utility used permissions that are no longer allowed with Mac OS X Tiger, so Tiger disables RetroRun on restart causing automatic backups to fail.

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

Considering that it's a different CPU then what Retrospect 6.1 was tested and qualified to work with, and a different version of Mac OS X then what Retrospect 6.1 was tested and qualified to work with, it's not unreasonable to observe problems.

It's actually pretty amazing that Retrospect works at all with Intel based Macs. If there turn out to be different issues with Woodcrest (and the version of OS X that those machine use) then there are with Core Duo (and/or Core2 Duo), that wouldn't surprise me.

Dave

I don't buy that. Sure, for some of the more uncommon hunks of code like talking to tape drives or whatever, but for general and common UI actions such as launching and asking for a password, any well-written app should have no problem doing that when running under Rosetta. The engineers only need to play by the rules when writing the code in the first place and not write any clever or sloppy hacks.

Quote

Link to comment

Share on other sites

waltr

Newbie

waltr

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

hi sjmills,

the KB article that you quote is article #7971. here is a link to it:

http://kb.dantz.com/article.asp?article=7971&p=2

the quote you cite may be taken out of context. here is the relevant context:

Quote:

EMC Dantz has provided a free update to Retrospect 6.0 for Macintosh customers that supports Apple's Mac OS X Tiger operating system.

Retrospect 6.1 for Macintosh adds full support for Mac OS X Tiger and is available as a free update for Retrospect 6.0 customers. This 6.1 version resolves the issues listed in this document. This update is available from

http://www.dantz.com/updates

Retrospect 6.0.204 and Mac OS X Tiger (Fixed in 6.1)

and then the passage you cite.

my recommendation would be _not_ to use Retrospect 6.0 with Tiger. there are known issues that cannot be resolved without an update. i _strongly_ recommend using Retrospect 6.1 with Tiger.

cheers.

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

I guess I was confused about which version the article was talking about. I am using 6.1.126 and see the problems I've described.

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

Then after a restart it failed to automatically run the backups. I found a blurb in the knowledge base that said that was a known bug. Then when ever I'd launch Retrospect, it would sometimes crash LaunchRetro or LaunchRetroHlper right after entering my password (I've always had the "Always require password" turned on). Now it *always* crashed after entering my password. So I can't even do a manual backup! This is most annoying.

I think it would be helpful to break-out the issue of Retrospect not auto-launching in advance of scheduled scripts from the issue of the program failing to launch at all. The former is often reported, while the latter is more unique.

- If you move your configuration file to the Desktop, does the program launch?

- You state "it would sometimes crash LaunchRetro or LaunchRetroHlper right after entering my password." Can you describe exactly what you were doing, and exactly what you saw when you did it (for example, how were you tracking the crash of LaunchRetroHlper)?

If fresh preferences didin't make a difference, I'd make a safe copy of your preference file, then use the Retrospect installer to un-install the program and then re-install.

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

I think it would be helpful to break-out the issue of Retrospect not auto-launching in advance of scheduled scripts from the issue of the program failing to launch at all. The former is often reported, while the latter is more unique.

- If you move your configuration file to the Desktop, does the program launch?

- You state

"it would sometimes crash LaunchRetro or LaunchRetroHlper right after entering my password."

Can you describe exactly what you were doing, and exactly what you saw when you did it (for example, how were you tracking the crash of LaunchRetroHlper)?

It launches, stops at the login dialog, when I enter my password and hit return, I get this in console.log:

Sep 25 16:35:47 Screamer crashdump[24562]: LaunchRetroHlper crashed

Sep 25 16:35:47 Screamer crashdump[24562]: crash report written to: /Users/tut/Library/Logs/CrashReporter/LaunchRetroHlper.crash.log

Sep 25 16:35:53 Screamer crashdump[24564]: LaunchRetroHlper crashed

Sep 25 16:35:53 Screamer crashdump[24564]: crash report written to: /Users/tut/Library/Logs/CrashReporter/LaunchRetroHlper.crash.log

This was tested just now after moving my "Retro.Config (6.0)" out of /Library/Preferences/Retrospect/. I also checked Operations Log and nothing gets written to that file before it crashes.

Quote:

If fresh preferences didin't make a difference, I'd make a safe copy of your preference file, then use the Retrospect installer to un-install the program and then re-install.

I'll try that later and let you know.

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 25, 2006

- Report
- Share

Posted September 25, 2006

Quote:

It launches, stops at the login dialog, when I enter my password and hit return, I get this in console.log:

Sep 25 16:35:47 Screamer crashdump[24562]: LaunchRetroHlper crashed

Sep 25 16:35:47 Screamer crashdump[24562]: crash report written to: /Users/tut/Library/Logs/CrashReporter/LaunchRetroHlper.crash.log

Sep 25 16:35:53 Screamer crashdump[24564]: LaunchRetroHlper crashed

Sep 25 16:35:53 Screamer crashdump[24564]: crash report written to: /Users/tut/Library/Logs/CrashReporter/LaunchRetroHlper.crash.log

And? What is shown in those two log files?

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 26, 2006

- Report
- Share

Posted September 26, 2006

Here are the contents of all 4 Retrospect .crash.logs. Good luck, cuz they're Rosettacized.

===================================

LaunchRetroHlper.crash.log:

Host Name: Screamer

Date/Time: 2006-09-20 23:01:22.025 -0500

OS Version: 10.4.7 (Build 8K1124)

Report Version: 4

Command: LaunchRetroHlper

Path: /Library/Preferences/Retrospect/LaunchRetroHlper

Parent: RetroRunSL [128]

Rosetta: Yes

Version: ??? (???)

PID: 965

Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0xa602089c

Thread 0 Crashed:

0 LaunchRetroHlper 0xb80ea49b spin_lock_wrapper + 49171

1 LaunchRetroHlper 0xb8065e89 0xb8000000 + 417417

2 LaunchRetroHlper 0xb80f587a spin_lock_wrapper + 95218

3 LaunchRetroHlper 0xb80f5aa3 spin_lock_wrapper + 95771

4 LaunchRetroHlper 0xb80f4a79 spin_lock_wrapper + 91633

5 LaunchRetroHlper 0xb805a1b1 0xb8000000 + 369073

6 LaunchRetroHlper 0xb805a2d1 0xb8000000 + 369361

7 LaunchRetroHlper 0xb80defbf spin_lock_wrapper + 2871

8 LaunchRetroHlper 0xb80df26b spin_lock_wrapper + 3555

9 LaunchRetroHlper 0xb80f33e2 spin_lock_wrapper + 85850

10 LaunchRetroHlper 0xb80050f7 0xb8000000 + 20727

11 LaunchRetroHlper 0xb80f28ef spin_lock_wrapper + 83047

12 LaunchRetroHlper 0xb80de9df spin_lock_wrapper + 1367

13 LaunchRetroHlper 0xb80038f2 0xb8000000 + 14578

14 LaunchRetroHlper 0xb8003819 0xb8000000 + 14361

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0xa602087c ebx: 0xb80ea35d ecx: 0xb7fff99c edx: 0x9329fa0c

edi: 0xb7ffd658 esi: 0x85bff058 ebp: 0xb7fff8a8 esp: 0xb7ffb400

ss: 0x0000001f efl: 0x00010286 eip: 0xb80ea49b cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:

0x8fc00000 - 0x8fc50fff dyld 46.9 /usr/lib/dyld

0x8fe00000 - 0x8fe49fff dyld 46.9 /usr/lib/dyld

0xb8000000 - 0xb827cfff LaunchRetroHlper /Library/Preferences/Retrospect/LaunchRetroHlper

Translated Code Information:

NO CRASH REPORT

==============================================

RetroRun.crash.log:

Host Name: Screamer

Date/Time: 2006-09-20 23:11:48.593 -0500

OS Version: 10.4.7 (Build 8K1124)

Report Version: 4

Command: RetroRun

Path: /Library/StartupItems/RetroRun/RetroRun

Parent: SystemStarter [1032]

Rosetta: Yes

Version: ??? (???)

PID: 1035

Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0x9329fa0c

Thread 0 Crashed:

0 RetroRun 0xb80ea496 spin_lock_wrapper + 49166

1 RetroRun 0xb8065e89 0xb8000000 + 417417

2 RetroRun 0xb80f587a spin_lock_wrapper + 95218

3 RetroRun 0xb80f5aa3 spin_lock_wrapper + 95771

4 RetroRun 0xb80f4a79 spin_lock_wrapper + 91633

5 RetroRun 0xb805a1b1 0xb8000000 + 369073

6 RetroRun 0xb805a2d1 0xb8000000 + 369361

7 RetroRun 0xb80defbf spin_lock_wrapper + 2871

8 RetroRun 0xb80df26b spin_lock_wrapper + 3555

9 RetroRun 0xb80f33e2 spin_lock_wrapper + 85850

10 RetroRun 0xb80050f7 0xb8000000 + 20727

11 RetroRun 0xb80f28ef spin_lock_wrapper + 83047

12 RetroRun 0xb80de9df spin_lock_wrapper + 1367

13 RetroRun 0xb80038f2 0xb8000000 + 14578

14 RetroRun 0xb8003819 0xb8000000 + 14361

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00000001 ebx: 0xb80ea35d ecx: 0xb7fff99c edx: 0x9329fa0c

edi: 0xb7ffd658 esi: 0x85bff058 ebp: 0xb7fff8a8 esp: 0xb7ffb400

ss: 0x0000001f efl: 0x00010286 eip: 0xb80ea496 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:

0x8fc00000 - 0x8fc50fff dyld 46.9 /usr/lib/dyld

0x8fe00000 - 0x8fe49fff dyld 46.9 /usr/lib/dyld

0xb8000000 - 0xb827cfff RetroRun /Library/StartupItems/RetroRun/RetroRun

Translated Code Information:

NO CRASH REPORT

=====================================================

RetroRunSL.crash.log:

Host Name: Screamer

Date/Time: 2006-09-23 00:08:21.851 -0500

OS Version: 10.4.7 (Build 8K1124)

Report Version: 4

Command: RetroRunSL

Path: /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/RetroRunSL.app/Contents/MacOS/RetroRunSL

Parent: WindowServer [94]

Rosetta: Yes

Version: 1.0.0 ()

PID: 1558

Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0x00000000

Thread 0 Crashed:

0 com.dantz.RetroRunSL 0xb80de3e9 spin_lock_try_wrapper + 901

1 com.dantz.RetroRunSL 0xb80e7800 spin_lock_wrapper + 37752

2 com.dantz.RetroRunSL 0xb80e1e77 spin_lock_wrapper + 14831

3 com.dantz.RetroRunSL 0xb80e682b spin_lock_wrapper + 33699

4 com.dantz.RetroRunSL 0xb80eae6a spin_lock_wrapper + 51682

5 com.dantz.RetroRunSL 0xb80ec7aa spin_lock_wrapper + 58146

6 com.dantz.RetroRunSL 0xb80664b9 0xb8000000 + 419001

7 com.dantz.RetroRunSL 0xb80f58c8 spin_lock_wrapper + 95296

8 com.dantz.RetroRunSL 0xb80f5aa3 spin_lock_wrapper + 95771

9 com.dantz.RetroRunSL 0xb80f4a79 spin_lock_wrapper + 91633

10 com.dantz.RetroRunSL 0xb805a1b1 0xb8000000 + 369073

11 com.dantz.RetroRunSL 0xb805a2d1 0xb8000000 + 369361

12 com.dantz.RetroRunSL 0xb80defbf spin_lock_wrapper + 2871

13 com.dantz.RetroRunSL 0xb80df26b spin_lock_wrapper + 3555

14 com.dantz.RetroRunSL 0xb80f33e2 spin_lock_wrapper + 85850

15 com.dantz.RetroRunSL 0xb80050f7 0xb8000000 + 20727

16 com.dantz.RetroRunSL 0xb80f28ef spin_lock_wrapper + 83047

17 com.dantz.RetroRunSL 0xb80de9df spin_lock_wrapper + 1367

18 com.dantz.RetroRunSL 0xb80038f2 0xb8000000 + 14578

19 com.dantz.RetroRunSL 0xb8003819 0xb8000000 + 14361

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0xb80de3d0 ecx: 0x00000000 edx: 0x00000d03

edi: 0x00000000 esi: 0x00000d03 ebp: 0xb7fff6d8 esp: 0xb7fff690

ss: 0x0000001f efl: 0x00010246 eip: 0xb80de3e9 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:

0x8fc00000 - 0x8fc50fff dyld 46.9 /usr/lib/dyld

0x8fe00000 - 0x8fe49fff dyld 46.9 /usr/lib/dyld

0xb8000000 - 0xb827cfff com.dantz.RetroRunSL 1.0.0 () /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/RetroRunSL.app/Contents/MacOS/RetroRunSL

Translated Code Information:

NO CRASH REPORT

=====================================================

retrospectd.util.crash.log:

Host Name: Screamer

Date/Time: 2006-09-24 02:14:30.088 -0500

OS Version: 10.4.7 (Build 8K1124)

Report Version: 4

Command: retrospectcd.util

Path: /System/Library/Filesystems/retrospectcd.fs/Contents/Resources/../../retrospectcd.util

Parent: diskarbitrationd [72]

Rosetta: Yes

Version: ??? (???)

PID: 2833

Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0x00000000

Thread 0 Crashed:

0 retrospectcd.util 0xb80de3e9 spin_lock_try_wrapper + 901

1 retrospectcd.util 0xb80e7800 spin_lock_wrapper + 37752

2 retrospectcd.util 0xb80e1e77 spin_lock_wrapper + 14831

3 retrospectcd.util 0xb80e682b spin_lock_wrapper + 33699

4 retrospectcd.util 0xb80eae6a spin_lock_wrapper + 51682

5 retrospectcd.util 0xb80ec7aa spin_lock_wrapper + 58146

6 retrospectcd.util 0xb80664b9 0xb8000000 + 419001

7 retrospectcd.util 0xb80f58c8 spin_lock_wrapper + 95296

8 retrospectcd.util 0xb80f5aa3 spin_lock_wrapper + 95771

9 retrospectcd.util 0xb80f4a79 spin_lock_wrapper + 91633

10 retrospectcd.util 0xb805a1b1 0xb8000000 + 369073

11 retrospectcd.util 0xb805a2d1 0xb8000000 + 369361

12 retrospectcd.util 0xb80defbf spin_lock_wrapper + 2871

13 retrospectcd.util 0xb80df26b spin_lock_wrapper + 3555

14 retrospectcd.util 0xb80f33e2 spin_lock_wrapper + 85850

15 retrospectcd.util 0xb80050f7 0xb8000000 + 20727

16 retrospectcd.util 0xb80f28ef spin_lock_wrapper + 83047

17 retrospectcd.util 0xb80de9df spin_lock_wrapper + 1367

18 retrospectcd.util 0xb80038f2 0xb8000000 + 14578

19 retrospectcd.util 0xb8003819 0xb8000000 + 14361

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0xb80de3d0 ecx: 0x00000000 edx: 0x00000d03

edi: 0x00000000 esi: 0x00000d03 ebp: 0xb7fff6d8 esp: 0xb7fff690

ss: 0x0000001f efl: 0x00010246 eip: 0xb80de3e9 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:

0x8fc00000 - 0x8fc50fff dyld 46.9 /usr/lib/dyld

0x8fe00000 - 0x8fe49fff dyld 46.9 /usr/lib/dyld

0xb8000000 - 0xb827cfff retrospectcd.util /System/Library/Filesystems/retrospectcd.fs/retrospectcd.util

Translated Code Information:

NO CRASH REPORT

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 26, 2006

- Report
- Share

Posted September 26, 2006

These seem to be all over the map in regards to the times of the crashes.

But one thing that stands out is the "retrospectcd.fs" filesystem plugin crash. I'd suggest removing this software (it allows members of CD/DVD Backup Sets to mount on the Desktop), and see if that makes a difference.

You can use the Retrospect installer to Un-Install, then do a custom install set to add just the application. Make sure you either don't un-install the preferences, or that you have a safe backup of your prefs file.

Dave

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 26, 2006

- Report
- Share

Posted September 26, 2006

Quote:

These seem to be all over the map in regards to the times of the crashes.

But one thing that stands out is the "retrospectcd.fs" filesystem plugin crash. I'd suggest removing this software (it allows members of CD/DVD Backup Sets to mount on the Desktop), and see if that makes a difference.

You can use the Retrospect installer to Un-Install, then do a custom install set to add just the application. Make sure you either don't un-install the preferences, or that you have a safe backup of your prefs file.

Did that, didn't help. Same crash in LaunchRetroHlper. after giving password. Oddly, the installer also crashes after giving the password, but launching it a 2nd time bypasses the password request and goes straight to the installer window.

The installer could not uninstall retrospectcd.fs, so I had to delete that by hand. I did not re-install it.

Sure would be nice if you'd release a Universal build so we could at least see where it's crashing, rather than the useless-to-end-user Rosette crash log.

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 26, 2006

- Report
- Share

Posted September 26, 2006

Quote:

Oddly, the installer also crashes after giving the password, but launching it a 2nd time bypasses the password request and goes straight to the installer window.

Well, at least that proves that the problem you are having is not with Retrospect. The installer is a VISE bundle, using entirely independent code from what EMCInsignia uses for their program.

When you launched it a second time, it was not authenticated. That's why it didn't work as expected.

- Were you running the installer program from a network share?

Quote

Link to comment

Share on other sites

Newbie

sjmills

Posted September 26, 2006

- Report
- Share

Posted September 26, 2006

Quote:

- Were you running the installer program from a network share?

No, from the boot drive.

If this is all some Rosetta-related problem, then one might assume that getting an Intel build and installer to the customers would fix it and we could actually get our data backed up. So, any estimated ship date? Even a vague one?

Quote

Link to comment

Share on other sites

Newbie

CallMeDave

Posted September 26, 2006

- Report
- Share

Posted September 26, 2006

Quote:

If this is all some Rosetta-related problem, then one might assume that getting an Intel build and installer to the customers would fix it and we could actually get our data backed up

The fact that your machine is having authentication issues with two completely different software applications (Retrospect and InstallerVISE) suggests the possibility of some localized configuration problem.

Your hardware is new, and the system software it is running is new, but basic trouble-shooting techniques are still valid. Booting from a clean install of OS X (from an external drive, for example) and installing/testing would be a good first start, to isolate system software from hardware. But it seems apparent from the posts on the Forum that Retrospect can be installed and run on MacPro machines withouth the problem's you're seeing.

Quote

Link to comment

Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest

Reply to this topic...

× Pasted as rich text. Paste as plain text instead

Only 75 emoji are allowed.

× Your link has been automatically embedded. Display as a link instead

× Your previous content has been restored. Clear editor

× You cannot paste images directly. Upload or insert images from URL.

Loading...

×

Share

Go to topic listing

×

×

Create New...