#1 Burning Software

1) What StarBurn SDK version are you running?

2) Can you send full debug log to [email protected]?

Initially sounds like PC is running out of virtual memory. For a reason...

The DLL is version 12.0.0.272. I'll send a log file as soon as I can generate one.

It appears that my client no longer has the debug version of this DLL. Can you provide it?

I managed to track down a debug version of the DLL and reproduce the error. Here is a log file from that batch. The error, of course, occurs at the end.

Thanx,

We are checking this issue!

Regards,

Dmitry

Any progress on this?

Hello,

Sorry for delay, there were holidays in our country.
I analysed your log and saw that before first failure were created two device objects with default (for write) cache size. And these device objects weren't destroyed before you tried to create next one. And you used "zero" cache size for device object creation - it's default value for writing (160 MBs). Possibly you didn't have enough free memory at this moment.
Are you using "zero" value of cache parameter while you enumerating devices?

I'm not sure I understand your question... There is no "cache size" when we initially enumerate the available devices. All device handles are opened with a cache size of zero, though.

Okay, I'll give that a shot. I assume that when you say "enumerate", you actually mean "open the device".

It looks like that worked, thanks!

Ok

Hello again.

Unfortunately it appears that this problem has actually not been solved. It turns out that the problem still exists, it just takes longer for it to surface now (110+ discs instead of 20+ discs). Once again it seems to be that there is a memory leak in Starburn, or perhaps in the driver for the BDR-206D.