On Sat, 01 Sep 2012 11:56:39 +0200, wim delvaux wrote: > I do run on a 64 bit OS with 8GB of memory but Pan consumes several GB > of memory ( 3 ish) > > I finally got my system back up by selecting "delete all selected > messages" on the group that causes the crash. > > This emptied the group and now it works again. > > W > > On Saturday 01 September 2012 10:50:10 Heinrich Müller wrote: >> Am 01.09.2012 02:04, schrieb wim delvaux: >> > Hi all, >> > >> > for some reason pan crashes when I want to open a group containing >> > lots of messages. >> > >> > I ran 0.139 in gdb to see if I could collect a stack dump but when >> > the crash occurs, there is no stack to be inspected. I compiled the >> > 139 release using CLAGS and CXXFLAGS=-g but it does not seem to be >> > enough. >> > >> > I also ran it through valgrind but it takes to damn long ... however >> > I noticed lots of overruns (accessing bytes outside of the allocated >> > memory) >> > >> > at the end you can find one such an example >> >> There's no help until I implement a database backend. The error stems >> from pan itself allocating too much memory. I guess you're running pan >> in a 32bit environment and the RAM pan wants is more than your address >> space can handle. >> >> Cheers.
I am seeing the same thing with 0.139 on Mint 13 (mate), but the lockup seems to be heat related. Binary group has 108,000+ entries, upon click to enter the group processor core temp rises 16 to 18 degrees F. If downloads are in progress, tasks are stopped and the screen info goes away. Closing the application (pan), waiting a few seconds for the temp to drop and restarting pan continues the downloads, as if nothing happened. This is happening with an AMD Phenom II x 4 965 @3.4 Ghz with 8 gig of memory. Bob _______________________________________________ Pan-users mailing list Pan-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/pan-users
