Bug 440376 - Kate crashes when trying to close an unsaved file
Summary: Kate crashes when trying to close an unsaved file
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 21.07.80
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-07-29 06:11 UTC by Rahul Chowdhury
Modified: 2022-02-08 04:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rahul Chowdhury 2021-07-29 06:11:51 UTC
Application: kate (21.07.80)

Qt Version: 5.15.2
Frameworks Version: 5.84.0
Operating System: Linux 5.11.0-20-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: Ubuntu Impish Indri (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Tried to close Kate with unsaved changes to a new Untitled file.

- Unusual behavior I noticed:
Crashed while trying to quit.

- Custom settings of the application:
None

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault

[KCrash Handler]
#4  0x0000555bb8ebaa8b in qDeleteAll<__gnu_cxx::__normal_iterator<KateMDI::ToolView* const*, std::vector<KateMDI::ToolView*, std::allocator<KateMDI::ToolView*> > > > (end=..., begin=0x555bbbcb1600) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320
#5  qDeleteAll<std::vector<KateMDI::ToolView*, std::allocator<KateMDI::ToolView*> > > (c=std::vector of length 1, capacity 32 = {...}) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328
#6  KateMDI::MainWindow::~MainWindow (__vtt_parm=<optimized out>, this=<optimized out>, this=<optimized out>, __vtt_parm=<optimized out>) at ./kate/katemdi.cpp:778
#7  KateMainWindow::~KateMainWindow (this=<optimized out>, this=<optimized out>) at ./kate/katemainwindow.cpp:181
#8  0x0000555bb8ebaefd in KateMainWindow::~KateMainWindow (this=<optimized out>, this=<optimized out>) at ./kate/katemainwindow.cpp:203
#9  0x00007f646ecd1f23 in QObject::event (this=0x555bbb5e0be0, e=0x555bbc671e60) at kernel/qobject.cpp:1301
#10 0x00007f647045656d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#11 0x00007f646f7d7783 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x555bbb5e0be0, e=0x555bbc671e60) at kernel/qapplication.cpp:3632
#12 0x00007f646eca482a in QCoreApplication::notifyInternal2 (receiver=0x555bbb5e0be0, event=0x555bbc671e60) at kernel/qcoreapplication.cpp:1063
#13 0x00007f646eca7851 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x555bba31f4b0) at kernel/qcoreapplication.cpp:1817
#14 0x00007f646ecfec17 in postEventSourceDispatch (s=0x555bba41d5a0) at kernel/qeventdispatcher_glib.cpp:277
#15 0x00007f646cc8b8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f646ccded28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f646cc89023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f646ecfe274 in QEventDispatcherGlib::processEvents (this=0x555bba42e320, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007f646eca318b in QEventLoop::exec (this=this@entry=0x7ffdc8102820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x00007f646ecab674 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x00007f646f082520 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
#22 0x00007f646f7d76f9 in QApplication::exec () at kernel/qapplication.cpp:2824
#23 0x0000555bb8eaa4fe in main (argc=<optimized out>, argv=<optimized out>) at ./kate/main.cpp:699
[Inferior 1 (process 54611) detached]

Possible duplicates by query: bug 440343, bug 440257, bug 440175, bug 440137, bug 440136.

Reported using DrKonqi
Comment 1 Waqar Ahmed 2022-01-09 20:32:12 UTC
Hi, can you reproduce this with 21.12?
Comment 2 Bug Janitor Service 2022-01-24 04:37:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-02-08 04:37:18 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!