Bug 377887 - Crash when opening file from archive
Summary: Crash when opening file from archive
Status: RESOLVED WORKSFORME
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 16.12.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2017-03-21 13:49 UTC by Ovidiu-Florin BOGDAN
Modified: 2019-03-27 08:26 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Ark (16.12.3) crash while trying to preview a text file in an archive (4.29 KB, text/plain)
2017-03-26 10:25 UTC, Pekka Helenius
Details
Ark (16.12.3) output log with debug symbols (2.03 KB, text/plain)
2017-03-26 16:22 UTC, Pekka Helenius
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ovidiu-Florin BOGDAN 2017-03-21 13:49:58 UTC
Application: ark (16.12.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-13-generic x86_64
Distribution: Ubuntu Zesty Zapus (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Opened a binary file from the archive.
When asked if to open as text, I confirmed. Crash happened imediately after.

-- Backtrace:
Application: Arhivator (ark), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f975d8ca8c0 (LWP 14706))]

Thread 4 (Thread 0x7f973b7f7700 (LWP 14711)):
#0  0x00007f9759b3810d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f97541f3576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f97541f368c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f975a45cf2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f975a40688a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f975a233fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f9757a575c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f975a238c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9755eed6ca in start_thread (arg=0x7f973b7f7700) at pthread_create.c:333
#9  0x00007f9759b440ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f97413c9700 (LWP 14710)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x00007f9743477e44 in ?? () from /usr/lib/nvidia-378/libGLX_nvidia.so.0
#2  0x00007f9742195394 in ?? () from /usr/lib/nvidia-378/libnvidia-glcore.so.378.13
#3  0x00007f974347712c in ?? () from /usr/lib/nvidia-378/libGLX_nvidia.so.0
#4  0x00007f9755eed6ca in start_thread (arg=0x7f97413c9700) at pthread_create.c:333
#5  0x00007f9759b440ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f974b7c0700 (LWP 14708)):
#0  0x00007f9759b3810d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f97531cfc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f97531d18d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f974e34aed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f975a238c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f9755eed6ca in start_thread (arg=0x7f974b7c0700) at pthread_create.c:333
#6  0x00007f9759b440ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f975d8ca8c0 (LWP 14706)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x00007f9759a733ea in __GI_abort () at abort.c:89
#8  0x00007f9759e9456d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f9759e92316 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f9759e92361 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f9759e92579 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f975a21a8a2 in qBadAlloc() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f975a2bec2a in QString::reallocData(unsigned int, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f975a2bf3a4 in QString::append(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9725a2ff7a in Kate::TextBuffer::load(QString const&, bool&, bool&, int&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#16 0x00007f9725aa338f in KateBuffer::openFile(QString const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#17 0x00007f9725a9b61c in KTextEditor::DocumentPrivate::openFile() () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#18 0x00007f975d0c8101 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5
#19 0x00007f975d0c8f94 in KParts::ReadOnlyPart::openUrl(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5
#20 0x00007f9725a85e1e in KTextEditor::DocumentPrivate::openUrl(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#21 0x00007f973a3c3d9a in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/arkpart.so
#22 0x00007f973a3c509f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/arkpart.so
#23 0x00007f973a3b0ebe in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/arkpart.so
#24 0x00007f975a435359 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f975b0e035c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x00007f975b0e7b11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007f975a4088a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00007f975a40b02d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x00007f975a45cb03 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x00007f97541f3377 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007f97541f35e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f97541f368c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f975a45cf0f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x00007f975a40688a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x00007f975a40effc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x00005623674d91a3 in ?? ()
#37 0x00007f9759a5c3f1 in __libc_start_main (main=0x5623674d7a20, argc=2, argv=0x7ffe89f93718, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe89f93708) at ../csu/libc-start.c:291
#38 0x00005623674d9eda in _start ()

Possible duplicates by query: bug 374433.

Reported using DrKonqi
Comment 1 Elvis Angelaccio 2017-03-21 23:06:38 UTC
How big was the binary file? Seems to be a crash caused by a bad_alloc...

Anyway the whole "open binary as text file?" dialog should probably be reconsidered at some point.
Comment 2 Pekka Helenius 2017-03-26 00:26:58 UTC
This happens to me everytime, as well. Open an archive with Ark, double click any text file and Ark crashes *immediately*.

Reproducible: Always.

Happens with text files with a size of just a few hundred KBs or even a few hundred Bytes.

I have all default KDE apps such as Kate etc installed. Not sure what triggers the crash event.
Comment 3 Elvis Angelaccio 2017-03-26 09:53:12 UTC
@Fincer: your stacktrace is the same? Are you also using Ubuntu?
Comment 4 Pekka Helenius 2017-03-26 10:25:17 UTC
Created attachment 104739 [details]
Ark (16.12.3) crash while trying to preview a text file in an archive

Sorry, forgot to mention. My backtrace as an attachment. I'm using Arch Linux (x86_64). 

ark 16.12.3-1
plasma-framework 5.32.0-1

(These are newest packages available in Arch package repositories. As in general, I keep my system packages up-to-dated by daily basis)
Comment 5 Elvis Angelaccio 2017-03-26 12:51:30 UTC
Weird, I'm also on arch but I cannot reproduce. Does it crash with every archive format?

However, your backtrace is slightly different from Ovidiu's...
Comment 6 Pekka Helenius 2017-03-26 13:25:20 UTC
At least with tar.gz, zip, tar, rar, jar, 7z.

In other words: with every archive format I tried.

I also compiled & installed Ark from source (Extra branch), still crashes.
Comment 7 Pekka Helenius 2017-03-26 15:34:20 UTC
Is there anything else I could do to track down the issue?

It's strange that you don't have the issue at all while I do, though the KDE packages should (mostly) be identical on our systems.

As a general question: Does Ark try to open an external text editor for previewing or is it a in-built feature? I just want pin down all possibilities that could cause the crash.
Comment 8 Elvis Angelaccio 2017-03-26 15:41:38 UTC
Ark just loads the kate part, that's where the crash happens, apparently. You could with some other application that uses the kate part (konqueror? krusader?) and check whether the crash happens also there.
Comment 9 Pekka Helenius 2017-03-26 16:22:20 UTC
Created attachment 104745 [details]
Ark (16.12.3) output log with debug symbols

May do in some day. 

For the meanwhile, I compiled Ark with debug symbols (https://community.kde.org/KDE_Utils/Ark#Build_with_debug_symbols) and ran the program. Output...well..says nothing new but just for the sake of information, I've attached the log here.

As a workaround for now, I tell Ark to open all files in external applications (kate in this case, obviously). Settings -> Configure Ark
Comment 10 Elvis Angelaccio 2017-03-26 17:57:29 UTC
@Fincer: what about other file types? Does it also crash if you preview a .png or a .pdf in the archive?
Comment 11 Pekka Helenius 2017-03-26 18:08:31 UTC
png, jpg and cr2 work without problems. I couldn't test pdf as I use a Windows version of Adobe Acrobat Pro for that filetype on my Linux system.
Comment 12 Christoph Feck 2017-03-29 23:54:56 UTC
Fincer, what you see is bug 378100.
Comment 13 Pekka Helenius 2017-03-30 00:09:29 UTC
Well, I don't have amarok installed. Not sure about the other part, however. The bug you linked resembles the one discussed here (at least).
Comment 14 Christoph Feck 2017-03-30 00:11:24 UTC
The bug is not an amarok bug, but a breakage in libssl/libcrypto.
Comment 15 Pekka Helenius 2017-03-30 00:19:17 UTC
Oh, well then. I'll test that soon. Thanks for pointing out!
Comment 16 Edmund Kasprzak 2018-02-12 19:26:45 UTC
I tried to recreate it in various archives (zip, 7z, tar.gz) using various binary files, Ark opens these binaries as text without any crash.

Can you share some archive file that is causing the issue ?
Comment 17 Andrew Crouthamel 2019-03-12 03:40:32 UTC
I cannot reproduce either, could you please re-test and/or provide an archive that causes the failure?
Comment 18 Bug Janitor Service 2019-03-27 04:33:16 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 19 Ovidiu-Florin BOGDAN 2019-03-27 08:26:41 UTC
I didn't receive any notifications of any of the messages on this bug... Sorry for not replying.

I can't reproduce this anymore. If I encounter this again I'll reopen, or open another bug.