Summary: | Segmentation fault (version 5.9.3) when closing the full article | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Vladimir <vokalashnikov92> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | amantia, kozlik, vokalashnikov92 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Backtrace
Output to Konsole From Valgrind gdb (segmentation fault) |
Description
Vladimir
2018-12-02 03:48:01 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 Created attachment 116628 [details]
Backtrace
Created attachment 116629 [details]
Output to Konsole
Created attachment 116630 [details]
From Valgrind
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. 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 *** >*** 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. (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? 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 (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? Created attachment 116670 [details]
gdb (segmentation fault)
(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, 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 *** |