Bug 1091699 - [abrt] tigervnc: rfb::Logger::write(): vncviewer killed by SIGABRT
Summary: [abrt] tigervnc: rfb::Logger::write(): vncviewer killed by SIGABRT
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:fceb7fe1a612d93aea331e0d6ee...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-27 12:05 UTC by Roger Melton
Modified: 2014-05-23 11:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-23 11:03:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (11.37 KB, text/plain)
2014-04-27 12:05 UTC, Roger Melton
no flags Details
File: cgroup (171 bytes, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: core_backtrace (4.67 KB, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: dso_list (4.79 KB, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: environ (2.01 KB, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: limits (1.29 KB, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: maps (28.99 KB, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: open_fds (232 bytes, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: proc_pid_status (934 bytes, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details
File: var_log_messages (202 bytes, text/plain)
2014-04-27 12:06 UTC, Roger Melton
no flags Details

Description Roger Melton 2014-04-27 12:05:55 UTC
Description of problem:
I'm not really sure what happened.  I had several things going on.

- Host System: Browsing web pages in host firefox.
- Host System: Copying data from an external USB hard drive to an NFS mounted file system
- Host System: VNC viewer was open on another desktop but should have been idle.

I didn't notice VNC Viewer crashing because my XServer (KDE) appeared to crash and I was back at a KDM login prompt.

Version-Release number of selected component:
tigervnc-1.3.0-14.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        /usr/bin/vncviewer
crash_function: rfb::Logger::write
executable:     /usr/bin/vncviewer
kernel:         3.13.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (8 frames)
 #6 rfb::Logger::write at /usr/src/debug/tigervnc-1.3.0/common/rfb/Logger.cxx:54
 #7 rfb::LogWriter::info at /usr/src/debug/tigervnc-1.3.0/common/rfb/LogWriter.h:73
 #8 CleanupSignalHandler at /usr/src/debug/tigervnc-1.3.0/vncviewer/vncviewer.cxx:112
 #10 Fl_Preferences::~Fl_Preferences at Fl_Preferences.cxx:369
 #11 __cxa_finalize at cxa_finalize.c:56
 #12 __do_global_dtors_aux at /lib64/libfltk.so.1.3
 #13 ??
 #14 _dl_fini at dl-fini.c:252

Comment 1 Roger Melton 2014-04-27 12:05:59 UTC
Created attachment 890204 [details]
File: backtrace

Comment 2 Roger Melton 2014-04-27 12:06:01 UTC
Created attachment 890205 [details]
File: cgroup

Comment 3 Roger Melton 2014-04-27 12:06:02 UTC
Created attachment 890206 [details]
File: core_backtrace

Comment 4 Roger Melton 2014-04-27 12:06:04 UTC
Created attachment 890207 [details]
File: dso_list

Comment 5 Roger Melton 2014-04-27 12:06:05 UTC
Created attachment 890208 [details]
File: environ

Comment 6 Roger Melton 2014-04-27 12:06:07 UTC
Created attachment 890209 [details]
File: limits

Comment 7 Roger Melton 2014-04-27 12:06:09 UTC
Created attachment 890210 [details]
File: maps

Comment 8 Roger Melton 2014-04-27 12:06:10 UTC
Created attachment 890211 [details]
File: open_fds

Comment 9 Roger Melton 2014-04-27 12:06:12 UTC
Created attachment 890212 [details]
File: proc_pid_status

Comment 10 Roger Melton 2014-04-27 12:06:14 UTC
Created attachment 890213 [details]
File: var_log_messages

Comment 11 Tim Waugh 2014-04-28 10:42:48 UTC
It looks like it was already in the process of invoking destructors when it got the signal to clean up.

Maybe the signal handling needs checking.

Comment 12 Tim Waugh 2014-05-23 11:01:34 UTC
What's happened is that a signal, perhaps SIGTERM, has been received during the progress of exiting normally (i.e. 'Exit viewer').

The destructor rfb::Logger::~Logger(this=<logStdErr>) gets called before the destructor Fl_Preferences::~Fl_Preferences() which is the point at which the signal was handled.

The problem is the rfb::Logger::~Logger doesn't actually do anything:

Logger::~Logger() {
  // *** Should remove this logger here!
}

Comment 13 Tim Waugh 2014-05-23 11:03:18 UTC
Reported upstream:
  https://sourceforge.net/p/tigervnc/bug-tracker/153/


Note You need to log in before you can comment on or make changes to this bug.