[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #40693] GUI occasionally blocks on QClipboard
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #40693] GUI occasionally blocks on QClipboard when exiting |
Date: |
Sun, 24 Nov 2013 21:47:06 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 |
Follow-up Comment #3, bug #40693 (project octave):
I managed to catch this in gdb. For what it's worth, here is what the stack
looks like while it is stuck in this waiting to exit state:
#0 0x00007f5a2b10f843 in select () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f5a2a5c6e38 in QX11Data::clipboardWaitForEvent (this=<optimized
out>,
address@hidden, address@hidden,
address@hidden,
address@hidden, address@hidden)
at kernel/qclipboard_x11.cpp:596
#2 0x00007f5a2a5c9ac0 in QClipboard::event (this=<optimized out>,
e=<optimized out>)
at kernel/qclipboard_x11.cpp:945
#3 0x00007f5a2a54b75c in QApplicationPrivate::notify_helper
(address@hidden,
address@hidden, address@hidden)
at kernel/qapplication.cpp:4567
#4 0x00007f5a2a551dd0 in QApplication::notify (this=0x7fff1f1e5240,
receiver=0x1704360,
e=0x7fff1f1e5180) at kernel/qapplication.cpp:4353
#5 0x00007f5a29cd333d in QCoreApplication::notifyInternal
(this=0x7fff1f1e5240,
receiver=0x1704360, address@hidden) at
kernel/qcoreapplication.cpp:949
#6 0x00007f5a2a54c272 in sendEvent (event=0x7fff1f1e5180, receiver=<optimized
out>)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#7 QApplication::~QApplication (this=0x7fff1f1e5240, __in_chrg=<optimized
out>)
at kernel/qapplication.cpp:1111
#8 0x00007f5a2e38d105 in octave_start_gui (argc=8, argv=<optimized out>,
start_gui=<optimized out>) at ../../libgui/src/octave-gui.cc:185
#9 0x00007f5a2b04f995 in __libc_start_main (main=0x400950 <main(int,
char**)>, argc=8,
ubp_av=0x7fff1f1e54e8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fff1f1e54d8) at libc-start.c:260
#10 0x00000000004009df in _start ()
Of course none of this looks like any of our code is responsible for this
problem, but I never saw this behavior until yesterday I think.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40693>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/