From: chris elliott on
well, a normal wx app tidies up once the wxframe is deleted. I don't
understand your code, but it seems odd to reinitialise more than once.


chris

Lukasz Kosewski wrote:
> Hello all,
>
> I've attached an incredibly simple app I've written for WxWidgets
> 2.6.3 running on X11 (no GTK, Motif, etc.).
>
> You'll note it's a very stripped down version of the hworld test


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org
For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org

From: Vadim Zeitlin on
On Tue, 17 Oct 2006 17:44:26 -0400 Lukasz Kosewski <lkosewsk(a)gmail.com> wrote:

LK> Valgrind identifies most of the leaks as mallocs or callocs in
LK> XOpenDisplay, _Xenq, etc. so I figure that at the end of wxEntry,
LK> something X-related is not being de-allocated properly.

It would make sense to suppose that XOpenDisplay() only leaks if
XCloseDisplay() hasn't been called. The trouble is that I don't see where
is XCloseDisplay() called at all, it seems that wxX11 always leaks the
display pointer. It would really make sense to me if display was closed in
~wxApp. Am I missing anything?

LK> I'd be most grateful. I've attempted to compile WxX11 2.7.1, but there
LK> were compile errors with missing headers

You need X11 development headers, e.g. libx11-dev[el] package or something
like that.

Regards,
VZ

--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org
For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org