QT memory leak?
QT memory leak?
- Subject: QT memory leak?
- From: Ethan Funk <email@hidden>
- Date: Fri, 26 Nov 2004 19:43:19 -0700
I have been hunting down a memory leak in my code using the "leak"
utility. I didn't find the leak I was hunting for, (it ended up being
a thread I forgot to clean up), but it did reveal this:
------------------------------------------------------------------------
--
Process 4271: 6408 nodes malloced for 3526 KB
Process 4271: 2 leaks for 64 total leaked bytes.
Leak: 0x0112df00 size=32
0x0112f240 0x00291b14 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000
Call stack: [thread 91beb817]: | 0x0 | _pthread_body |
sessionThread__FP10threadPass | LoadFilePlayer__FUlPc |
load__10FilePlayerPc | openFileAsMovie__10FilePlayer | OpenMovieFile |
OpenMovieFile_priv | openMovieAlias | WFOpenRes_priv |
WarholResolveAlias_priv | WarholResolveAliasWithFlags_priv |
LMGetTheGDevice | GetThreadGDevice | GetQDThreadGlobals | calloc |
malloc_zone_calloc
------------------------------------------------------------------------
--
Is this a bug in the OpenMovieFile system call? The only thing I am
passing into this call is a pointer to a FSSpec structure, a pointer to
file reference number (short) and readonly flags, all of which live on
the stack as a local variables, so I don't know where the hemorrhage
is. The call doesn't return anything to me that I would have to
dispose of, so where else should I look. Could this be a bug in the
system call? It's not a very big leak, but I thought I would ask any
way.
I'm still having trouble with the VariSpeed AU for device to device
synchronization, if any one has words of wisdom on that topic.
Ethan...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden