Skip to content
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

Closed
cyberduck opened this issue Sep 18, 2012 · 23 comments
Closed

Regular crashes with Exited abnormally: Broken pipe on uploads #6863

cyberduck opened this issue Sep 18, 2012 · 23 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 18, 2012

a304470 created the issue

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:

Stack: (0x95bf0f4f 0x95afd432 0x2d032e9d 0x2d032c9e 0x2d02a814 0x2d02ae32 0x43aa2ea 0x43bd54c 0x430f2dc 0x43ba900 0x439ca38 0x43b9f84 0x43b9740 0x444c528 0x4372370 0x430f168 0x43ba900 0x439ca38 0x43b9f84 0x43b9740 0x43c4efc 0x43c54fc 0x43b8d74 0x4254dc0) 

And then:

9/18/12 8:57:49 AM com.apple.launchd[80] ([0x0-0x1e21e2].ch.sudo.cyberduck[41422]) Exited abnormally: Broken pipe 

I also cannot try the snapshot:

9/18/12 11:29:52 AM Cyberduck[56095] Sparkle Error: An error occurred while downloading the update. Please try again later. 
9/18/12 11:29:52 AM Cyberduck[56095] Sparkle Error (continued): file doesn’t exist 
9/18/12 11:29:52 AM Cyberduck[56095] Sparkle Error (continued): file doesn’t exist 

Let me know if you need a debug log.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 18, 2012

a304470 commented

I'll attach a cyberduck filtered debug console log - almost always a silent "crash" after an upload.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 19, 2012

a304470 commented

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 20, 2012

a304470 commented

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 24, 2012

@dkocher commented

Please update to the latest snapshot build (again) available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 24, 2012

@dkocher commented

Please reopen this ticket if the issue persists when running the snapshot build.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 24, 2012

a304470 commented

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 26, 2012

a304470 commented

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?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 26, 2012

@dkocher commented

Replying to [comment:7 blacktrash]:

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?

That could be. I will have to find a 10.5 installation do test.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 1, 2012

@dkocher commented

Fixed Java 5 interoperability in 8f2d910.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2012

a304470 commented

Replying to [comment:9 dkocher]:

Fixed Java 5 interoperability in 8f2d910.

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 ;-)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2012

@dkocher commented

Thanks for the feedback. I will do some more testing on 10.5 but will close this in the meantime.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 7, 2012

a304470 commented

Replying to [comment:11 dkocher]:

Thanks for the feedback. I will do some more testing on 10.5 but will close this in the meantime.

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.
Right now I simply don't have time to debug further, so leaving it at that.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 1, 2012

a304470 commented

Replying to [comment:11 dkocher]:

Thanks for the feedback. I will do some more testing on 10.5 but will close this in the meantime.

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 19, 2012

a304470 commented

Replying to [comment:13 blacktrash]:

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.

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).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 27, 2012

@dkocher commented

#6328 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 15, 2013

@dkocher commented

I can no longer reproduce this issue with the latest snapshot build available.

@cyberduck cyberduck closed this Apr 15, 2013
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2013

a304470 commented

Good that it works for you ;-)
For me Version 4.3 (10863) just crashed yet again after an upload.
imho MacOS 10.5.8 is not supported.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2013

@dkocher commented

Replying to [comment:20 blacktrash]:

Good that it works for you ;-)
For me Version 4.3 (10863) just crashed yet again after an upload.
Is this for S3 as reported originally?

imho MacOS 10.5.8 is not supported.
We will drop support for 10.5 in the next major release.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2013

@dkocher commented

Replying to [comment:20 blacktrash]:

Good that it works for you ;-)
For me Version 4.3 (10863) just crashed yet again after an upload.
imho MacOS 10.5.8 is not supported.

Please post the crash report.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 24, 2013

a304470 commented

There are no cyberduck logs at ~/Library/Logs/CrashReporter, that's the point, it's all silent. In spite of:

defaults read ch.sudo.cyberduck logging
debug

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 24, 2013

a304470 commented

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 25, 2013

@dkocher commented

Replying to [comment:24 blacktrash]:

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.

I cannot replicate this crash when editing metadata for a file in S3. Can you test with a different OS X user account.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 30, 2013

@dkocher commented

#6863 closed as duplicate.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants