On Sun, Apr 10, 2016 at 08:53:32AM -0700, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > 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: > > > > > Ever since doing the CVS update with this font size issue, Xastir's been > > > crashing somewhat randomly after hours of uptime, [...out of swap space...] > > > > > > 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.
I'll check it out. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
