381371 2017-06-18 16:56:35 +0000 KWrite crashed when closing a large HTML file 2017-06-25 12:22:37 +0000 1 1 2 Applications kate kwrite 17.04.2 Ubuntu Linux RESOLVED DUPLICATE 380114 drkonqi NOR crash --- 0 dennis.schridde kwrite-bugs-null christoph 0 oldest_to_newest 1683207 0 dennis.schridde 2017-06-18 16:56:35 +0000 Application: kwrite (17.04.2) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.8.0-53-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: 1. I opened a large HTML file (dump from facebook.com), which had much of its contents on one line 2. I tried to edit it, but KWrite proved too slow, with long pauses when trying to mark text using the mouse, and long reaction times to keystrokes 3. I clicked the close-window button (X) 4. KWrite took a while to react to it and then reacted by crashing -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbeeeddb900 (LWP 4567))] Thread 2 (Thread 0x7fbecffff700 (LWP 4599)): #0 0x00007fbeeb6a7b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fbee5c4a38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fbee5c4a49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fbeebfc775b in QEventDispatcherGlib::processEvents (this=0x7fbec80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x00007fbeebf720ba in QEventLoop::exec (this=this@entry=0x7fbecfffec90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x00007fbeebda1f64 in QThread::exec (this=this@entry=0x7fbeeeee6d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x00007fbeeee72735 in QDBusConnectionManager::run (this=0x7fbeeeee6d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x00007fbeebda6b48 in QThreadPrivate::start (arg=0x7fbeeeee6d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #8 0x00007fbee78b06ba in start_thread (arg=0x7fbecffff700) at pthread_create.c:333 #9 0x00007fbeeb6b382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fbeeeddb900 (LWP 4567)): [KCrash Handler] #6 0x000000000244b3e0 in ?? () #7 0x00007fbed74abea6 in qDeleteAll<QList<Phonon::MediaObject*>::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:323 #8 qDeleteAll<QList<Phonon::MediaObject*> > (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:331 #9 NotifyByAudio::~NotifyByAudio (this=0x28c9e00, __in_chrg=<optimized out>) at /workspace/build/src/notifybyaudio.cpp:46 #10 0x00007fbed74abf39 in NotifyByAudio::~NotifyByAudio (this=0x28c9e00, __in_chrg=<optimized out>) at /workspace/build/src/notifybyaudio.cpp:48 #11 0x00007fbeebf9d663 in QObjectPrivate::deleteChildren (this=this@entry=0x28c88a0) at kernel/qobject.cpp:1970 #12 0x00007fbeebfa6814 in QObject::~QObject (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:1041 #13 0x00007fbed7485309 in KNotificationManagerSingleton::~KNotificationManagerSingleton (this=<optimized out>, __in_chrg=<optimized out>) at /workspace/build/src/knotificationmanager.cpp:61 #14 (anonymous namespace)::Q_QGS_s_self::Holder::~Holder (this=<optimized out>, __in_chrg=<optimized out>) at /workspace/build/src/knotificationmanager.cpp:67 #15 0x00007fbeeb5e6ff8 in __run_exit_handlers (status=0, listp=0x7fbeeb9705f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #16 0x00007fbeeb5e7045 in __GI_exit (status=<optimized out>) at exit.c:104 #17 0x00007fbeeb5cd837 in __libc_start_main (main=0x4090f0 <main(int, char**)>, argc=1, argv=0x7ffd2162ddf8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd2162dde8) at ../csu/libc-start.c:325 #18 0x000000000040b769 in _start () Reported using DrKonqi 1685118 1 christoph 2017-06-25 12:22:37 +0000 :( Bad, duplicate of this, not nice. *** This bug has been marked as a duplicate of bug 380114 ***