regex win32 memory leaks

Hi, I am having a windows MFC app that dynamically links to the regex lib. On application shutdown the memory leak detection kicks in and diagnoses leaks in the regex dll. If I use the static lib everything seems to be fine. I have to admit that I don't have a clue what's going on. Any ideas? Thomas BTW this is vc-7.1 boost 1.31 -- Thomas Witt witt@acm.org

I am having a windows MFC app that dynamically links to the regex lib. On application shutdown the memory leak detection kicks in and diagnoses leaks in the regex dll. If I use the static lib everything seems to be fine.
I have to admit that I don't have a clue what's going on. Any ideas?
Nope, no idea either. However one thing that can happen: the regex library initializes itself when it's first used, but then doesn't free itself until the program exits, in fact with a dll regex lib, the regex cleanup occurs after your exe has terminated doesn't it? So maybe this "asynchronous" behaviour could the cause of your problems, but I can't be sure. John.

I am having a windows MFC app that dynamically links to the regex lib. On application shutdown the memory leak detection kicks in and diagnoses leaks in the regex dll. If I use the static lib everything seems to be fine.
I have to admit that I don't have a clue what's going on. Any ideas?
Nope, no idea either. However one thing that can happen: the regex
"John Maddock" <john@johnmaddock.co.uk> wrote in message news:01d301c48125$edf75940$3c520352@fuji... library
initializes itself when it's first used, but then doesn't free itself until the program exits, in fact with a dll regex lib, the regex cleanup occurs after your exe has terminated doesn't it? So maybe this "asynchronous" behaviour could the cause of your problems, but I can't be sure.
I would assume that Thomas sees that the leak is always the same size. I've found this to be a common occurrence with VC in debug mode when using dlls that allocate memory on startup, and don't free until after VC's memory debugger has reported the leak. I recently saw a newsgroup posting that purported to have a 'fix' for this issue. Unfortunately I can't remember(oldtimers disease) the newsgroup, or the message text. I'm sure it was within the last month somewhere under microsoft.public.* or comp.os.*. I'll see if I can track it down. Jeff F
participants (3)
-
Jeff Flinn
-
John Maddock
-
Thomas Witt