New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regular crashes with Exited abnormally: Broken pipe on uploads #6863
Comments
I'll attach a cyberduck filtered debug console log - almost always a silent "crash" after an upload. |
Observations: seems to be happening (mostly) when I don't close the transfer window and do something else like setting permissions, or start a new transfer without closing the transfer window beforehand. |
It would be nice to have this but at least acknowledged in some way. I am also willing to provide further info if needed. btw, I gave a donation (under a different email address /blacktrash/ /at/ /gmx/ /dot/ /org/), so a quick short answer is appreciated while I have to return to the aws console - hopefully only for the time being. |
Please reopen this ticket if the issue persists when running the snapshot build. |
Thanks. Unfortunately with the snapshot. I am stuck in a vicious crash - offer of notification - relaunch circle. I can't even test it. I trashed all preferences, reinstalled 4.2.1, licensed it, installed snapshot - vicious circle again. |
I remember the symptoms from an application which was not backwards compatible with MacOS 10.5.8 (Leopard) - could that be the case for the snapshot too? |
Replying to [comment:7 blacktrash]:
That could be. I will have to find a 10.5 installation do test. |
Replying to [comment:9 dkocher]:
That seems to do the trick so far. Thanks. I did not have the opportunity to do some thorough testing, but if anything comes up, I just come back here ;-) |
Thanks for the feedback. I will do some more testing on 10.5 but will close this in the meantime. |
Replying to [comment:11 dkocher]:
Unfortunately it just happened again. Once after an upload, and once after file info. The upload seems to have completed (video seems undamaged), but the upload window shows 0 kb transferred, transfer incomplete, which is definitely wrong. |
Replying to [comment:11 dkocher]:
I'm still experiencing crashes unfortunately. Not always, but sometimes. It seems to be related to overwriting files. I tried turning the confirmation dialogue off, but that did not seem to help either. Will now switch back to debug mode to hopefully get a crash log. |
Replying to [comment:13 blacktrash]:
In case you're still listening, yes, I can confirm that the crashes always happen when overwriting. Just checked with latest nightly build 4.2.2 (10582). |
Good that it works for you ;-) |
Replying to [comment:20 blacktrash]:
|
Replying to [comment:20 blacktrash]:
Please post the crash report. |
There are no cyberduck logs at ~/Library/Logs/CrashReporter, that's the point, it's all silent. In spite of:
|
Currently a 100% reliable way to make it crash is to try to edit metadata in the info window. Not possible. - Yes, that's all for S3. |
Replying to [comment:24 blacktrash]:
I cannot replicate this crash when editing metadata for a file in S3. Can you test with a different OS X user account. |
Cyberduck works great! ... as long as it works :-( Unfortunately it crashes extremley often, mainly just before finishing an upload or when invoking or working with the file info.
I am currently only using it for AWS S3.
After that the log is empty.
I have tons of messages in the Console log like this one:
And then:
I also cannot try the snapshot:
Let me know if you need a debug log.
Attachments
cyberduck.log.tar.bz2
(26.2 KiB)The text was updated successfully, but these errors were encountered: