Hi!
The behavior Darren was describing got me thinking of valgrind. Is
anyone regularly (or occasionally) testing LyX using valgrind? (If
anyone's not familiar with valgrind: it's an open source runtime memory
checker which does a lot more than just memory checking, for example, I
believe it can also be used for profiling. See http://valgrind.org/.) It
could help find a lot of nasty problems...
I just tried running LyX under it now, to see what happens... It seems
like there is memory leaking, I'm not sure how significant it is,
though. (It would require a little work to get valgrind *usefully*
running --- like excluding reports from underlying libraries, etc. But
someone familiar with the code may find it useful.)
One interesting point, though: running LyX under valgrind is very very
slow. This is normally annoying, but it may actually be helpful in
simulating a slow system, for bugs reported about those. For example,
it's interesting to try some typing with and without Peter's patch
(event_2.patch) for scrolling! I don't know if this would really be
useful, but it might...
HTH!
Dov
