Jump to content

Will Retrospect 8 cure 'not enough memory' messages?

Recommended Posts

Running Retrospect 6.1, I get regular 'not enough memory' messages (error -108). Sometimes Retrospect then continues OK to the next machine, sometimes the backup terminates.


Before upgrading to Retrospect 8, I need to know the cause, and would be grateful for comments.





Retrospect 6.1.230 Server version - this is the only application running apart from the system software.

Mac mini, 1.83 GHz Intel Core Duo, 2 Gb RAM, Mac OS X 10.5.8

Tandberg VXA-320 Firewire StorageLoader

Backing up about 12 networked computers (Mac OS X 10.4 or 10.5), including 2 servers running OS X Server


Message in Console at the time when the problem occurs:

15/12/2009 23:13:55 Retrospect[14990] Retrospect(14990,0xa09b6820) malloc: *** mmap(size=147025920) failed (error code=12)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

Edited by Guest
  • Like 1
Link to comment
Share on other sites

I think it would be almost impossible to get anything from Activity Monitor. We would only know there was an issue after the event, when Retrospect reports that the backup failed. Activity Monitor shows real time scenarios.


I understand what you mean about Rosetta, but I would have thought that 2 Gb was enough for Retrospect 6.1 since this is the only application running.

Link to comment
Share on other sites

  • 2 years later...
  • 8 months later...

Join the conversation

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

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.

  • Create New...