Summary: | KIO HTTP crashes opening https:// URLs | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Elias Probst <mail> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kdelibs-bugs, markg85, misc-kdeorg, nate, sitter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Elias Probst
2015-01-10 00:20:19 UTC
Hi, I just tried to reproduce this problem, but it doesn't seem to crash here. Could you verify if this crash still occurs? KIO version i used: 5.10 Plasma 5.3 Regards, Mark Crash cannot be reproduced in my PPA-KDE (kio 5.22, Plasma 5.6.4), however, there is a massive delay (75s in both tries) between executing the command mentioned in the initial post and the browser receiving the URL and loading it. This was just filed under bug 364662. Works just fine for me with KDE Frameworks 5.49. I can actually reproduce this. With firefox as browser and simply running `kioclient5 exec http://networkcheck.kde.org` after a while the slave will exit and crash during exit. What's more, I even know why. Threaded applications shouldn't call exit() as it doesn't terminate threads so it a) breaks life time expectations and b) runs cleanup handlers while other threads potentially are still going about their business. The tricky thing here of course is that we want to absolutely terminate because of how the dispatch loop of the slaves work. So the likely only solution here is to use quick_exit() instead, disadvantage there is that it does vastly less cleanup. Perhaps David has a better idea? From what I see in the code this is a tricky problem because when the slave's exit is called we should force-terminate ASAP, but there is no way to do that safely if multiple threads are involved. Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! 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! 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! |