GNOME Bugzilla – Bug 542535
crash in Document Viewer: Viewing the PDF document...
Last modified: 2008-07-13 20:45:13 UTC
Version: 2.20.2 What were you doing when the application crashed? Viewing the PDF document whose bittorrent hash is: DCFEC4E085812B6239C96D6F1F76258AF24E0E11 Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 334225408 vsize: 334225408 resident: 63623168 share: 13717504 rss: 63623168 rss_rlim: 18446744073709551615 CPU usage: start_time: 1215785498 rtime: 264 utime: 238 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b618caee820 (LWP 27482)] [New Thread 0x40800950 (LWP 27485)] (no debugging symbols found) 0x00002b6187596edf in waitpid () from /lib/libpthread.so.0
+ Trace 202560
Thread 1 (Thread 0x2b618caee820 (LWP 27482))
----------- .xsession-errors (191449 sec old) --------------------- ConnectDisconnectManager::address exception: full=/249.55.185.90:50001, hostname=249.55.185.90, port=50001, unresolved=false, full_sub=249.55.185.90/249.55.185.90, host_address=249.55.185.90 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=0.0.0.0/0.0.0.0, local_port=0, remote_address=<null>, remote_port=0 TCPConnectionManager::mainLoop::212,TCPConnectionManager::access$900::46,TCPConnectionManager$5::runSupport::202,AEThread::run::71 java.net.SocketException: Invalid argument at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.addNewRequest(TCPConnectionManager.java:311) at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.addNewOutboundRequests(TCPConnectionManager.java:242) at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.mainLoop(TCPConnectionManager.java:212) at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.access$900(TCPConnectionManager.java:46) at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager$5.runSupport(TCPConnectionManager.java:202) at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:71) DEBUG::Wed Jul 09 01:00:56 GMT-08:00 2008::com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager::addNewOutboundRequests::242: ConnectDisconnectManager::address exception: full=/241.188.15.116:3560, hostname=241.188.15.116, port=3560, unr ...Too much output, ignoring rest... --------------------------------------------------
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 415714 ***