Bug 243076

Summary:	Kalzium crashed after closing it
Product:	[Applications] kalzium	Reporter:	fsanchez <franciscoadriansanchez>
Component:	general	Assignee:	Kalzium Developers <kalzium>
Status:	RESOLVED INTENTIONAL
Severity:	crash	CC:	etienne.rebetez, franciscoadriansanchez
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description fsanchez 2010-06-28 21:20:57 UTC

Application: kalzium (2.3.80)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-22-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
I have just installed Kalzium for seeing how it works. I finished my test and closed it. Then, the crash report window appeared.

 -- Backtrace:
Application: Kalzium (kalzium), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f30a846d7a0 (LWP 9007))]

Thread 2 (Thread 0x7f30934c6710 (LWP 9010)):
#0  0x00007f30a31b1f53 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f309ecc24a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f309ecc28fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f30a4a3c406 in QEventDispatcherGlib::processEvents (this=0x1c92080, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f30a4a116c2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f30a4a11a9c in QEventLoop::exec (this=0x7f30934c5d70, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f30a49208db in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007f30a49f1dd8 in QInotifyFileSystemWatcherEngine::run (this=0x1c88910) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f30a4922f95 in QThreadPrivate::start (arg=0x1c88910) at thread/qthread_unix.cpp:248
#9  0x00007f30a46929ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007f30a31be6cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f30a846d7a0 (LWP 9007)):
[KCrash Handler]
#5  0x0000000000000021 in ?? ()
#6  0x00007f30a660c450 in Avogadro::UndoSequence::~UndoSequence() () from /usr/lib/libavogadro-kalzium.so.0
#7  0x00007f30a4232e6f in qDeleteAll<QList<QUndoCommand*>::const_iterator> (this=0x321fe50) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:322
#8  qDeleteAll<QList<QUndoCommand*> > (this=0x321fe50) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:330
#9  QUndoStack::clear (this=0x321fe50) at util/qundostack.cpp:499
#10 0x00007f30a4232fd6 in ~QUndoStack (this=0x321fe50, __in_chrg=<value optimized out>) at util/qundostack.cpp:473
#11 0x00007f30a4a2188c in QObjectPrivate::deleteChildren (this=0x31071b0) at kernel/qobject.cpp:1986
#12 0x00007f30a3c0cc0d in ~QWidget (this=0x30fb9a0, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1476
#13 0x000000000045685a in _start ()

Reported using DrKonqi

Comment 1 Etienne 2010-06-29 18:32:59 UTC

Thanks for the bugreport.
Just some questions:
Can you remember what you did during the test?
Can you reproduce the bug?

Etienne

Comment 2 fsanchez 2010-06-29 21:00:18 UTC

(In reply to comment #1)
> Thanks for the bugreport.
> Just some questions:
> Can you remember what you did during the test?
> Can you reproduce the bug?
> 
> Etienne

I just checked some functionalities like calculations, the content of the information of elements and the molecular editos.

The crash reporter apperar once I closed Kalzium.

I opened it again, did quite the same things and it didn't crashed, so I assume I can't reproduce it.

Comment 3 fsanchez 2010-07-21 20:49:13 UTC

Created attachment 49368 [details]
New crash information added by DrKonqi

I have could reproduce it this time. I used the Molecule Editor for several molecules today. Then I close it and then I close Kalzium from the X button. 2 secons after, the crash report appeared as in the first report.

Comment 4 Etienne 2012-09-24 08:58:50 UTC

I can't reproduce that chrash. The reported version is quit old now so I goint to close the bug.