| Summary: | Konqueror Folder View Crash (Dolphin Dropbox plugin) | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Joachim Mairböck <j.mairboeck> |
| Component: | plugins: dropbox | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dolphin-bugs-null, emmanuelpescosta099, erik_hahn, simonandric5, valorie.zimmerman |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.12.95 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/dolphin-plugins/671b27877b22b0e9ba3dd2bdaa0a3909c501161f | Version Fixed In: | 4.13.0 |
| Sentry Crash Report: | |||
| Attachments: |
Console output from crash
Valgrind log New crash information added by DrKonqi |
||
|
Description
Joachim Mairböck
2014-03-23 18:16:48 UTC
Thanks for the bug report. @Emmanuel: it seems that Thomas Richard is still the default assignee for "plugins: dropbox". Shall I change that and make you the default assignee for this product? (dolphin-bugs-null is currently always added as CC automatically for new reports, and I think we should keep that). > Shall I change that and make you the default assignee for this product? If you prefer it, yes. > dolphin-bugs-null is currently always added as CC automatically for new reports, and I think we > should keep that Yes definitely, just started watching this list ;) I'm afraid that we can't do anything about it in Dolphin. I think it is a bug in Qt, looks like fd_set, select, ... related problems. According to __chk_fail () there is a bufferoverflow somewhere?! http://refspecs.linux-foundation.org/LSB_4.0.0/LSB-Core-generic/LSB-Core-generic/libc---chk-fail-1.html Can you reproduce this crash? Thanks for your help! I had the same situation occur again yesterday, and it crashed again like this (I didn't inspect the stack trace though). I also haven't tested it in Dolphin alone, or at least it never occured to me there yet. Can you provide some more information? Any special settings? Does this problem occur randomly or after some specific time? High or normal memory usage in Konqueror? Big folders? Dropbox client version? ... Thanks for your help! I just tried opening my home folder (which contains my Dropbox folder) in standalone Dolphin. It crashed too, nearly instantly (after 2 seconds). So this is independent of Konqueror. DrKonqi didn't appear though. I have about 1.7 GB in my Dropbox folder, some of them are shared with others. Dropbox Version 2.6.5 I'll attach a log of the console output of Dolphin. Created attachment 85720 [details]
Console output from crash
@Joachim: Running Dolphin in Valgrind might help to identify the cause of the problem, but I'm not sure. In any case, it will make Dolphin quite slow, so I don't know if testing this will work reasonably. If you want to try it, have a look at http://community.kde.org/Dolphin/FAQ/Crashes Thanks for your help. (In reply to comment #2) > > Shall I change that and make you the default assignee for this product? > If you prefer it, yes. OK, I'll change that then. Thomas is not actively working on the plugin any more AFAIK, so IMHO it does not make much sense to have him as the default assignee. > > dolphin-bugs-null is currently always added as CC automatically for new reports, and I think we > should keep that > Yes definitely, just started watching this list ;) OK, that's good :-) Created attachment 85819 [details]
Valgrind log
I have tried running Dolphin under valgrind and attaching the log here.
Interestingly, DrKonqi appeared, which otherwise didn't happen when running Dolphin standalone.
Thanks for the Valgrind log! The interesting part seems to be this error output from the application: QObject: Cannot create children for a parent that is in a different thread. (Parent is QTcpSocket(0xcebfbac), parent's thread is QThread(0xad4fb88), current thread is UpdateItemStatesThread(0x110eafa0) KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit dolphin: Fatal IO error: client killed Apparently something in the UpdateItemStatesThread tries to create a child for a parent QObject that belongs to the main thread? *** Bug 332983 has been marked as a duplicate of this bug. *** Review-Request: https://git.reviewboard.kde.org/r/117344/ Needs testing, because I can't reproduce the crash. Thanks :) > Review-Request: https://git.reviewboard.kde.org/r/117344/
>
> Needs testing, because I can't reproduce the crash. Thanks :)
Works flawlessly.
(In reply to comment #13) > Works flawlessly. Great :) Thanks for testing! Git commit 3f0efce0517a0bc3bb0564fd3000889c67bce277 by Emmanuel Pescosta. Committed on 03/04/2014 at 00:03. Pushed by emmanuelp into branch 'master'. Fix crash on startup caused by Dropbox plugin Create the item state socket on "begin retrieval" and delete it again in "end retrieval". FIXED-IN: 4.13.0 REVIEW: 117344 M +3 -6 dropbox/fileviewdropboxplugin.cpp http://commits.kde.org/dolphin-plugins/3f0efce0517a0bc3bb0564fd3000889c67bce277 Git commit 671b27877b22b0e9ba3dd2bdaa0a3909c501161f by Emmanuel Pescosta. Committed on 03/04/2014 at 00:03. Pushed by emmanuelp into branch 'KDE/4.13'. Fix crash on startup caused by Dropbox plugin Create the item state socket on "begin retrieval" and delete it again in "end retrieval". FIXED-IN: 4.13.0 REVIEW: 117344 M +3 -6 dropbox/fileviewdropboxplugin.cpp http://commits.kde.org/dolphin-plugins/671b27877b22b0e9ba3dd2bdaa0a3909c501161f *** Bug 333185 has been marked as a duplicate of this bug. *** Created attachment 93569 [details]
New crash information added by DrKonqi
dolphin (15.04.0) on KDE Platform 4.14.6 using Qt 4.8.6
- What I was doing when the application crashed:
deleting some files in dolphin --- i have not used konqueror, nor i have any dropbox plugin (as far as i know)... all of a sudden this crash happen...
i use kubuntu-ci-unstable (wily) PPA,,,
nice day
Simon :)
-- Backtrace (Reduced):
#6 0x00007f5c15905267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7 0x00007f5c15906eca in __GI_abort () at abort.c:89
[...]
#9 0x00007f5c159e8e8c in __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7f5c15a5ed44 "buffer overflow detected") at fortify_fail.c:38
#10 0x00007f5c159e6e80 in __GI___chk_fail () at chk_fail.c:28
#11 0x00007f5c159e8dd7 in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:25
|