Re: ComboBox DeleteItem() not being called for all items?

On 12 Dec, 01:58, Giovanni Dicanio
<giovanniDOTdica...@xxxxxxxxxxxxxxxxx> wrote:
Giovanni Dicanio wrote:


Yay! No more "Memory leak detected".. I also had to remove void
CLpCombo::DeleteItem(LPDELETEITEMSTRUCT lpDeleteItemStruct) since it
was no longer needed.

Thanks again! Many of these classes were originally written win VC6 on
Win95 and I know that it did work then. Not sure when this error
reared it's ugly head, but it might have been when goign from 2000 to
Xp.
.

Relevant Pages

  • Memory leak in ADODB Connection15::Open method
    ... void CDBBase::CreateDBHandle ... Purify is showing a memory leak of 36 bytes in Connection15::Open method ... We are using MDAC version 2.81, Visual C++ .NET, Microsoft Development ...
    (microsoft.public.data.ado)
  • Re: Memory leak
    ... > void f ... There is no pointer pointing to it anymore, ... means you have no way of freeing it again: you created a memory leak. ... So the correct sequence in your example would be: ...
    (comp.lang.cpp)
  • Re: C++ is slow
    ... >> void main ... > If you use anything else besides 'int' return type ... > You have a memory leak. ... >> PROG II ...
    (comp.lang.cpp)
  • Re: obj function hello()
    ... gert wrote: ... Can you collaborated on the memory leak part please? ... void leak(size_t howmuch) { ...
    (comp.lang.c)
  • Re: ComboBox DeleteItem() not being called for all items?
    ... Giovanni Dicanio wrote: ... In this version, the CString pointer is not from lpDeleteItemStruct, instead it is just from GetItemData(), of course. ...
    (microsoft.public.vc.mfc)