[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] An irreproducible anomaly

From: Vadim Zeitlin
Subject: Re: [lmi] An irreproducible anomaly
Date: Tue, 14 Jun 2016 23:16:22 +0200

On Tue, 14 Jun 2016 21:03:14 +0000 Greg Chicares <address@hidden> wrote:

GC> On 2016-06-14 20:54, Vadim Zeitlin wrote:
GC> > On Tue, 14 Jun 2016 20:04:08 +0000 Greg Chicares <address@hidden> wrote:
GC> [...]
GC> > GC> My hypothesis is that the wxUpdateUIEvent pump has failed. But
GC> > GC> I find no call to SetUpdateInterval() or SetMode() in lmi that
GC> > GC> could cause UpdateUI events to stop flowing.
GC> > 
GC> >  Yes, I don't see why would this happen. If you can reproduce this again,
GC> > could you please check if the in-place text edit control in the census 
GC> > remains open while the "Edit" dialog is shown or is it closed first for 
GC> > too?
GC> I believe the report stated that in-place edit control remained open.

 This does seem to confirm my idea that we're somehow ending up showing the
dialog from inside wxYield() call. As calling wxSafeYield() from inside
wxYield() does nothing (which was considered to be "safer" than yielding
recursively and crashing with stack overflow), this could explain the
observed symptoms. I still don't see how can we end up inside wxYield() in
the first place though... Had you done something else before seeing this
problem? I suspect that the real bug must be elsewhere, and this is just a
consequence of it, but it's nothing more than a suspicion unfortunately.
But if you could remember which operations you had performed before seeing
the bug, it might provide a way of reproducing it.

 Thanks in advance,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]