[akregator] [Bug 401638] New: Segmentation fault (version 5.9.3) when closing the full article

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

Bug ID: 401638
Summary: Segmentation fault (version 5.9.3) when closing the
full article
Product: akregator
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: general
Assignee: kdepim-***@kde.org
Reporter: ***@gmail.com
Target Milestone: ---

SUMMARY
Hello! In openSUSE Tumbleweed, Akregator (ver 5.9.3), the program crashes if
you close the tab with the full version of the article opened from the RSS
feed.

STEPS TO REPRODUCE
01. Add rss feed.
02. Update rss feed.
03. Options "additional", do not put a tick "download when viewing the entire
article" and "mark all new articles as read."
04. Options "store 100 articles" from the rss feed.
05. Open any article in the rss feed.
06. Read to the end of the "short version of the article."
07. Click the "full article".
08. Go to the open tab with the article.
09. Close the tab with the article.
10. 3..2..1.. Segmentation fault.

OBSERVED RESULT
Segmentation fault.

EXPECTED RESULT
Correct closing of the tab with the full version of the article. The program
remains in working condition.

SOFTWARE/OS VERSIONS
openSUSE Tumbleweed 20181129
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
I follow the topic, if you need to add some information, then let me know.

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

Vladimir <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=401638

Christoph Feck <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |crash
Status|REPORTED |NEEDSINFO
Resolution|--- |BACKTRACE

--- Comment #1 from Christoph Feck <***@kde.org> ---
If the crash is reproducible, please add the backtrace for the crash. For more
information, please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #2 from Vladimir <***@gmail.com> ---
Created attachment 116628
--> https://bugs.kde.org/attachment.cgi?id=116628&action=edit
Backtrace

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #3 from Vladimir <***@gmail.com> ---
Created attachment 116629
--> https://bugs.kde.org/attachment.cgi?id=116629&action=edit
Output to Konsole

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #4 from Vladimir <***@gmail.com> ---
Created attachment 116630
--> https://bugs.kde.org/attachment.cgi?id=116630&action=edit
From Valgrind

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

Vladimir <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|BACKTRACE |---
Status|NEEDSINFO |REPORTED

--- Comment #5 from Vladimir <***@gmail.com> ---
Good day, Christoph Feck. Thank you for your prompt reply, I fulfilled your
request for additional information. I hope that it is comprehensive and
descriptive. If not, please let me know what else you can do.

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=401638

Christoph Feck <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|REPORTED |RESOLVED

--- Comment #6 from Christoph Feck <***@kde.org> ---
Thanks, the backtrace is useful. Unfortunately, it is deep in QtWebEngine
instead of in KDEPIM components.

*** This bug has been marked as a duplicate of bug 399299 ***

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

Vladimir <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |REPORTED

Post by Christoph Feck
*** This bug has been marked as a duplicate of bug 399299 ***

"-- Information about the crash:
- What I was doing when the application crashed:
When I middle click on a link (open in external browser) then akregator crash.
But if I right click and select 'open in external browser' in the submenu it
works without the crash.

The crash can be reproduced every time."

(c) Karel Kozlík (https://bugs.kde.org/show_bug.cgi?id=399299#c0)

Dear Christoph Feck, I looked at bug 399299. First, the playback actions are
different. Secondly, that bug is not reproduced in me. If you follow the steps
described by Karel Kozlík, the program will continue to work correctly. Due to
these circumstances, please look again whether it is worth giving the bug the
status of "RESOLVED DUPLICATE". Many thanks for your work.

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #8 from Vladimir <***@gmail.com> ---
(In reply to Christoph Feck from comment #6)

Unfortunately, it is deep in QtWebEngine instead of in KDEPIM components.

In addition to the previous comment, I would like to clarify whether I need to
change the information in the Product column? If so, what should be indicated?

[Karel Kozlík]

https://bugs.kde.org/show_bug.cgi?id=401638

Karel Kozlík <***@kufr.cz> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kufr.cz

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #9 from Vladimir <***@gmail.com> ---
Created a corresponding error message. Please correct me in the comments if
something is wrong with him and/or vote if you think that the bug should be
fixed as soon as possible, thanks.
Link 1: https://bugreports.qt.io/browse/QTBUG-72260

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #10 from Vladimir <***@gmail.com> ---
(In reply to Christoph Feck from comment #6)

Post by Christoph Feck
Thanks, the backtrace is useful. Unfortunately, it is deep in QtWebEngine
instead of in KDEPIM components.

"Probably KDEPIM is deleting it's interceptor on the main thread before
QtWebEngine is done using it on the IO thread. That is not a bug in
QtWebEngine, just hard-to-use API.
...
Basically, like other properties of the profile, the interceptor should be set
before the profile is put to use and not changed while the profile lives. That
is what is missing in the documentation. But it's definitely documented that
the interceptor is called on the IO thread, and KDEPIM does not take this into
account either." (с) Jüri Valdmann
(
https://bugreports.qt.io/browse/QTBUG-72260?focusedCommentId=437042&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-437042
)

A bug on the side of KDEPIM, Christoph Feck?

[Vladimir]

https://bugs.kde.org/show_bug.cgi?id=401638

--- Comment #11 from Vladimir <***@gmail.com> ---
Created attachment 116670
--> https://bugs.kde.org/attachment.cgi?id=116670&action=edit
gdb (segmentation fault)