R12 CD Ripper crash

[TarkusShakti]

WinXP fully updated as of this morning
2 cpus & 1Gb of memory
R12 & m4a up-to-date

While ripping a 30:02 (mm:ss) track, CD Ripper used all available memory then crashed WinXP. There were "no available memory" errors from two other applications and from the OS.

CDGrab.exe displayed the following error message window:
window title:
Microsoft Visual c++ Runtime Lib

window message:
Program <path2program./CDGrabber.exe
This application has requested the Runtime to terminate it in an unusual way. Please contact the application Support team for more info.

CDGrab was still on the first track and displayed "Pass1 ripping 99%"

Three other applications were crashed. I was unable to do anything except close the error window and launch taskmanager for a restart.

TS

[TarkusShakti]

Re: R12 CD Ripper crash

2nd try at the above cd.

This time CDGrab didn't crash, but three other applications did, including Explorer (the desktop version, not the file browser.) The OS displayed another Virtual memory error.

I had 504Mb of memory available when I started CD ripper. The crash happened after the second track had started ripping.

The OS did not crash.

This CD seems to bring out the worst in R12...

TS

[Spoon]

Re: R12 CD Ripper crash

Try ripping to wave, instead of m4a (with inherent complexities).

[bhoar]

Re: R12 CD Ripper crash

What are your paging settings on that machine?

-brendan

[TarkusShakti]

Re: R12 CD Ripper crash

What are your paging settings on that machine?

-brendan

I have a 1.5Gb paging file (forced by use of ZoneAlarm.)

TS

[bhoar]

Re: R12 CD Ripper crash

I have a 1.5Gb paging file (forced by use of ZoneAlarm.)

TS

Hmm, that should be sufficient. My suggestion would be to watch both the virtual memory size and the memory used* of the largest process and note the approximate values at various points such as program startup, beginning of rip, end of first track rip, end of first track encode ... problem encountered, etc.

You might also notice there's another process that appears to grow substantially as the dbpoweramp process does its work, such as an antivirus utility, and that interaction might be the cause of some of the problems.

-brendan

* the task manager value for the latter can be misleading. I suggest using Process Explorer instead and track the following: Private bytes, Virtual Size, Working Set, Working Set Private, WS Shareable and WS Shared (in that order of priority, you can probably ignore the last three).