On Sunday, April 10, 2016 8:17:20 AM PDT Ken Koster wrote:
> On Sunday, April 10, 2016 7:42:02 AM PDT Tom Russo wrote:
> > On Sat, Apr 09, 2016 at 07:07:43AM -0700, we recorded a bogon-computron
> > collision of the
...
> > It gets worse, though.
> >
> > Ever since doing the CVS update with this font size issue, Xastir's been
> > crashing somewhat randomly after hours of uptime, with no helpful
> > information ("Killed" is all the shell says). No core drop or anything.
> > The reason is hidden in the syslog: "out of swap space." This is on a
> > machine with 24 GB of RAM and no swap, with nothing other than Xastir
> > running at the times when it crashes.
> >
> > So clearly there's a memory leak somewhere. I don't have time to track it
> > down myself. So in my local copy, I've just reverted to revision 1.122 of
> > draw_symbols.c.
>
> I will check it out, I have an idea where it might be and that I missed
> doing some magick that was done in the previous version.Fixed it! At least I think I did. Xastir seems stable on my system where the previous version clearly had a continuous uptick in memory usage. I missed needing to free up some font info. That's what comes from not 100% understanding the original code. The latest rev is in CVS. Still noodling on the proportional font issue. -- Ken - N7IPB Email: [email protected] JID: [email protected] PGP Sig: F42B EF90 3CD3 31C7 3056 122E 993A 7B2E 5138 C42A "I have now exceeded my BFS (Budget For Stupid) for the month" - Me to WE7U
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
