Bug 401638 - Segmentation fault (version 5.9.3) when closing the full article
Summary: Segmentation fault (version 5.9.3) when closing the full article
Status: RESOLVED DUPLICATE of bug 371511
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-02 03:48 UTC by Vladimir
Modified: 2018-12-14 20:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backtrace (44.21 KB, text/plain)
2018-12-02 16:58 UTC, Vladimir
Details
Output to Konsole (1.67 KB, text/plain)
2018-12-02 17:00 UTC, Vladimir
Details
From Valgrind (660.33 KB, text/plain)
2018-12-02 17:01 UTC, Vladimir
Details
gdb (segmentation fault) (517 bytes, text/plain)
2018-12-04 10:57 UTC, Vladimir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir 2018-12-02 03:48:01 UTC
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.
Comment 1 Christoph Feck 2018-12-02 04:40:03 UTC
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
Comment 2 Vladimir 2018-12-02 16:58:49 UTC
Created attachment 116628 [details]
Backtrace
Comment 3 Vladimir 2018-12-02 17:00:23 UTC
Created attachment 116629 [details]
Output to Konsole
Comment 4 Vladimir 2018-12-02 17:01:45 UTC
Created attachment 116630 [details]
From Valgrind
Comment 5 Vladimir 2018-12-02 17:07:41 UTC
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.
Comment 6 Christoph Feck 2018-12-03 01:58:41 UTC
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 ***
Comment 7 Vladimir 2018-12-03 03:58:58 UTC
>*** 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.
Comment 8 Vladimir 2018-12-03 04:06:08 UTC
(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?
Comment 9 Vladimir 2018-12-04 06:32:08 UTC
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
Comment 10 Vladimir 2018-12-04 10:33:48 UTC
(In reply to Christoph Feck from comment #6)
> 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?
Comment 11 Vladimir 2018-12-04 10:57:55 UTC
Created attachment 116670 [details]
gdb (segmentation fault)
Comment 12 András Manţia 2018-12-13 15:49:15 UTC
https://phabricator.kde.org/D17563
Comment 13 Vladimir 2018-12-13 21:21:30 UTC
(In reply to András Manţia from comment #12)
> https://phabricator.kde.org/D17563

Good day, András Manţia. Thank you very much(!), and the whole team.

Respectfully,
Comment 14 András Manţia 2018-12-14 20:47:06 UTC
Let's track this in 371511, as it is older and is the same issue.

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