Sharp as a Marble - Super light blogging today

<< Gun Myths - A gun won't help you in an ambush | Home | The arsenal >>

I finally found a workaround for a bug in some code we had. I'm the only one who understands the stuff and this needs to be in place before I leave to go take care of my mom.

I just discovered a memory leak.

$#@^&*

posted @ 9/26/2007 9:57:40 AM

Comments

Boyd says:

on 9/26/2007 2:24:28 PM

I just hate it when my memory takes a leak on my code. Er...or something like that.

Nomen Nescio says:

on 9/26/2007 6:09:45 PM

ah, the wonder of garbage collection. i am so darn glad to be writing in a high-level language at times. ;-)

Robb Allen says:

on 9/26/2007 6:27:17 PM

Nomen, I'm writing .Net and unfortunately what I need to do isn't supported, so I have to manage threading on my own since I'm trying to run UI components in a background service. I have a legitimate reason for doing so, trust me.

The problem is that .Net (thankfully) runs MTA by default. A UI runs Single Threaded Apartment so that the UI can discuss things amongst itself, while background workers take care of the busy work. I need to take a visual of the UI and turn it into a JPEG, so that means I need to create a thread, switch the apartment model to STA, run the code and shove the bitmap into a static variable (assuring that other processes don't write to the same variable), then wipe it clean.

Unfortunately, even forcing Garbage Collection misses the objects created on the new thread. Now I have to find out why and fix it.

Excedrin is my friend.

Boyd says:

on 9/27/2007 11:42:34 AM

Just more proof that UIs are evil.

Even more evil than assault weapons, believe it or not.

Comments have been closed on this topic.