#1 Burning Software

1)Can you provide as with your code where you are using our SDK?
Maybe you don't destroy all toolkit objects which you use.

2)We will try to burn over 200 discs and will detect memory leaks if them exist.
-What disc type do you use?
-What disc capacity do you use?
-How much data do you burn?
-What file system type(ISO 9660, ISO 9660 + Joliet, UDF) do you use?

1. Aside from the change you suggested, the code is identical to what has already been posted...
We open with:
result = StarBurn_CdvdBurnerGrabber_Create(&m_Handle, textresult, sizeof(textresult), &sysresult, &cdbinfo, (PCALLBACK) StarBurnCallback, this, m_PortId, m_BusId, m_TargetId, m_LUN, STARBURN_CACHE_SIZE_READ_ONLY);
We close with:
StarBurn_Destroy(&m_Handle);
I imagine that the log file I posted will verify that all handles are being released once their affiliated actions are completed.

2. We are not burning discs, we are ripping them.

Please correct me.
You ripping discs using StarBurn_CdvdBurnerGrabber_GrabTrack ?

That depends on the user. If they select ISO mode, then the application uses either GrabCD or GrabDVD. If the user selects file mode then fread is used.

We performed a lot of tests, but memory leaks wasn't detected.
Currently you use ASPI transport protocol, please try SPTI (StarBurn_CdvdBurnerGrabber_CreateEx) or SPTD (StarBurn_CdvdBurnerGrabber_CreateExEx). I'm not sure, but maybe it help.

Jtrammell,

Can you provide us with logs where you reproduced this issue last time?

Alexander,

I'll see what I can do. I'm not sure we really have the budget to be taking shots in the dark, though...

Andrey,

Here is the log again.

It's old log file. Which we have already discussed.
We need a new one, where you have already fixed device enumeration.