Ahh, was meant to be v 3.9 leaks, not indicating the number of leaks.
No, all remaining leaks look like they are CRT.
Ex:
Routine Name Source File Unit Name Source Line
Class Name
HeapAlloc 0
_heap_alloc_base MALLOC.C malloc.obj 47
_nh_malloc_dbg_impl DBGHEAP.C dbgheap.obj 232
_calloc_dbg_impl DBGHEAP.C dbgheap.obj 586
_wsetenvp STDENVP.C wstdenvp.obj 77
__tmainCRTStartup CRT0.C wwincrt0.obj 171
wWinMainCRTStartup CRT0.C wwincrt0.obj 154
And
Routine Name Source File Unit Name Source Line
Class Name
HeapAlloc 0
_heap_alloc_base MALLOC.C malloc.obj 47
_nh_malloc_dbg_impl DBGHEAP.C dbgheap.obj 232
_calloc_dbg_impl DBGHEAP.C dbgheap.obj 586
_ioinit IOINIT.C ioinit.obj 110
__tmainCRTStartup CRT0.C wwincrt0.obj 171
wWinMainCRTStartup CRT0.C wwincrt0.obj 154
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, July 19, 2014 2:44 PM
To: wix-devs@lists.sourceforge.net
Subject: Re: [WiX-devs] appsyn feed: documentation
I was concerned when I saw that your branch had "39 memory leaks..." Do the 63
leaks start in WiX/Burn?
Maybe I'll put the RC2 build through AppVerifier...
On 19-Jul-14 15:33, Hoover, Jacob wrote:
Now if only I could cleanup the 63 CRT heap leaks...
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, July 19, 2014 2:27 PM
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] appsyn feed: documentation
Merged. Thanks!
On 19-Jul-14 15:19, Hoover, Jacob wrote:
Leaks put into their own PR, https://github.com/wixtoolset/wix3/pull/118
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, July 19, 2014 2:03 PM
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] appsyn feed: documentation
On 19-Jul-14 14:54, Hoover, Jacob wrote:
Yeah, but I have a branch out there for our discussed changes so WixBA uses the
engine atom feed parsing. Unfortunately, there are outstanding issues with the
existing WiX feed so the engine as is won't accept it (lacking the app id
throws out all the possible updates).
I'm sure Rob wouldn't mind if you fixed that too. :) You could do a cherry-pick
merge, I think.
I do wonder why we have a CoreInitialize but not a CoreUninitialize.
Pretty sure the standard is to have them only when they're needed.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
