CacheObject allocation error

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

Good morning,

I have an application which is happily running on hundreds of Winows XP computers with a wide variety of configurations. It has recently begun to be installed on Windows 7 computers and we are seeing a problem with Starburn on these installations. It only occurs in Windows 7, and it only occurs when using Pioneer BDR-206D optical drives. The problem is that after the application has been running for a while (typically after processing somewhere between 20 and 30 discs) the following function call fails:

Code:

result = StarBurn_CdvdBurnerGrabber_Create(&m_Handle, textresult, sizeof(textresult), &sysresult, &cdbinfo, (PCALLBACK) StarBurnCallback, this, m_PortId, m_BusId, m_TargetId, m_LUN, 0);

It fails with the following error message:

Quote:

Error 4 'CStarBurn_CacheObject::CStarBurn_CacheObject(): Failed to allocate memory'

Our application always (to the best of my knowledge, and given that the problem only occurs in Windows 7 with a specific drive I believe this is true) releases the allocated drive handle thusly:

Code:

StarBurn_Destroy(&m_Handle);

Since we do allocate and release the drive handles several times per disc, it would seem there is a memory leak in Starburn. Further evidence of this can be seen when comparing the starting memory usage of the application (1,588K) with the memory usage at the point of failure in Starburn (900,000K+).

Is this a known issue? Is there a known or anticipated fix?

anton (staff) · **Posted:** Wed Apr 24, 2013 7:19 pm

1) What StarBurn SDK version are you running?

2) Can you send full debug log to support@starburnsoftware.com?

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

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

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

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

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

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

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.

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Thanx,

We are checking this issue!

Regards,

Dmitry

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

Any progress on this?

andrey(staff) · **Joined:** Fri Jan 26, 2007 4:31 pm **Posts:** 452

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?

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

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.

andrey(staff) · **Joined:** Fri Jan 26, 2007 4:31 pm **Posts:** 452

jtrammell wrote:

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.

Zero is a special value that tells the toolkit to allocate default cache size (160 MB).
Please use define STARBURN_CACHE_SIZE_READ_ONLY for enumeration and STARBURN_CACHE_SIZE_READ_WRITE when you use object for burning.

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

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

andrey(staff) · **Joined:** Fri Jan 26, 2007 4:31 pm **Posts:** 452

jtrammell wrote:

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

"Enumerate" - I mean you get the list of the optical drives to show it to the user. And you open(create object) each device with some cache size.

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

It looks like that worked, thanks!

andrey(staff) · **Joined:** Fri Jan 26, 2007 4:31 pm **Posts:** 452

jtrammell · **Joined:** Wed Dec 07, 2011 4:20 pm **Posts:** 18

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.

#1 Burning Software

CacheObject allocation error

Who is online