Bug 343305 – Pan crashes periodically

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 343305 - Pan crashes periodically


Summary:	Pan crashes periodically


Status:	RESOLVED DUPLICATE of bug 343257

Product:	Pan
Classification:	Other
Component:	general
Version:	pre-1.0 betas
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Charles Kerr
QA Contact:	Pan QA Team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-05-29 16:37 UTC by alen_williams
Modified:	2006-06-18 01:54 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description alen_williams 2006-05-29 16:37:45 UTC

Steps to reproduce:
I've queued up a bunch of stuff to download. Pan runs for a while, then, just
disappears! It doesn't seem to be linked to any action I'm taking. If I start it
again, it picks where it left off, runs for a while, then, gone...

Stack trace:
Script started on Sun 28 May 2006 02:07:06 PM PDT
[root@einstein tmp]# uname -a
Linux einstein.address4life.com 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST
2006 i686 i686 i386 GNU/Linux
[root@einstein tmp]# gdb pan
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".

(gdb) handle SIGUSR1 nostop noprint
Signal        Stop	Print	Pass to program	Description
SIGUSR1       No	No	Yes		User defined signal 1
(gdb) handle SIG32 nostop noprint 
Signal        Stop	Print	Pass to program	Description
SIG32         No	No	Yes		Real-time event 32
(gdb) run
Starting program: /usr/bin/pan 
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x70c000
[Thread debugging using libthread_db enabled]
[New Thread -1208453456 (LWP 26572)]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

Program received signal SIGABRT, Aborted.
[Switching to Thread -1208453456 (LWP 26572)]
0x0070c402 in __kernel_vsyscall ()
(gdb) thread apply all bt

+ Trace 68514

Thread 1 (Thread -1208453456 (LWP 26572))

#0 __kernel_vsyscall
#1 raise
from /lib/libc.so.6
#2 abort
from /lib/libc.so.6
#3 __gnu_cxx::__verbose_terminate_handler
from /usr/lib/libstdc++.so.6
#4 std::set_unexpected
from /usr/lib/libstdc++.so.6
#5 std::terminate
from /usr/lib/libstdc++.so.6
#6 __cxa_throw
from /usr/lib/libstdc++.so.6
#7 operator new
from /usr/lib/libstdc++.so.6
#8 std::vector<char, std::allocator<char> >::reserve
at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/ext/new_allocator.h line 88
#9 pan::TaskArticle::use_nntp
at task-article.cc line 196
#10 pan::Task::give_nntp
at task.cc line 43
#11 pan::Queue::process_task
at queue.cc line 191
#12 pan::Queue::upkeep
at queue.cc line 110
#13 (anonymous namespace)::queue_upkeep_timer_cb
at pan.cc line 69
#14 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 (anonymous namespace)::run_pan_in_window
at pan.cc line 103
#20 main
at pan.cc line 251

The program is running.  Exit anyway? (y or n) y
[root@einstein tmp]# exit

Script done on Sun 28 May 2006 05:30:55 PM PDT


Other information:

Comment 1 Elijah Newren 2006-05-31 00:07:45 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 343257 ***