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
Crash when closing edited file before upload completes #2377
Comments
Same issue here with nigthly build. |
I'm pretty sure I'm having the same problem. I'll pay attention from now on to see if it's always when switching focus to Cyberduck, but it definitely crashes all the time for no percievable reason other than normal use. Luckily nothing gets corrupted or anything, but it really slows me down and breaks my flow. I'm also using Smultron, could this be a smultron specific problem? Are people having this problem wiht other editors? |
Not Smultron related IMHO, using TextMate here. |
I'm experiencing this too. It definitely is connected to using a text editor and files being edited must be reopened fresh when cyberduck is restarted. This also happens randomly where I can hit command+s and smultron indicates the files is saved (icon changes amber to white), but it doesn't update on the server. A third way I have relatively consistently noticed this bug is if you create a new file on the server, open it with smultron and paste in content. Hit save. close and reopen - nothing there. I'm not sure if this is connected to the crashes that occur, but I think there is a good chance it is a problem writing/reading memory between the two. Also FYI when cyberduck crashes with smultron open there is no message from apple or cyberduck indicating the failure of the program! This is very troublesome and may force me to change ftp clients if it isn't fixed soon. |
I can confirm this. For me this happens when closing the file in the editor before the upload and refresh of the directory listing has been completed. |
I think the fixed bug may be related to the last poster, but not the problem that many of the others and I are having. I'm pretty sure that a lot of the crashes I've been experiencing are from times when nothing was happening with cyberduck; like if I was using Firefox, clicked back to cyberduck to open a file and it crashes before I can do anything. I will try the nightly and see if it stops occurring. |
Sorry, but I just had this crash again with 5e5fa7e. Since you fixed a different bug with this ticket (the one the ticket title refers to) let me know and i'll repost this to a new ticket to keep things clean. Here's what I did to crash:
I always use the 'outline' view in cyberduck and make heavy use of the triangles for viewing a lot of content at once (in the above crash i had two levels of triangles opened). Could that potentially be part of the problem? Do you ever use the triangles? Anyone else with the problem use the triangles? I ask because I know there are a few other softer bugs with the triangles (sometimes they close for no reason when something refreshes and stuff). The crashes aren't directly linked to triangles, but that might be something causing some users not to have the problem (while others like me have it every few minutes it seems). I just retried the process above and after a few shots it crashed again, it feels like maybe some time has to pass with no activity (you're staring at something and not clicking) right before you bring CD into focus for it to crash. Obviously that's the most frustrating bug to try to recreate, but based on the descriptions of others it seems like maybe it is a time thing. Is there some kind of time limit after which CD stops holding memory or something? Thanks so much for working on this and for making Cyberduck the best FOSS ftp for mac, sorry that we're presenting you with such an annoying problem. |
Replying to [comment:8 jeremyclarke]:
I have reopened #2142 to track the issue initially described. |
I've been having the same problem every day for the last few weeks. I'm updating to the nightly build every morning. It still isn't working properly. It doesn't necessarily seem as though its crashing when I close an edited file. It appears random. Sometimes I just tab back to Cyberduck and "POOF" its gone. |
I am also having this problem with the 4166 build. It appears to occur when switching programs with command+tab, but it is very sporadic. I haven't been able to figure out what triggers it. |
Just installed the newest update and Cyberduck still crashed. It happend, when I tried to drag an image-file via exposé to a folder in Cyberduck. Just when I was about to drop it into the directory on the server Cyberduck suddenly disappeared/crashed. Another bug that I experieced but might be fixed with the newest update was the following: I edited a file with skEdit, saved it, switched directly to Safari to reload the page and got the message from the server, that the requested file wasen't found. I looked in Cyberduck and appearantly, Cyberduck seemed to have deleted it. |
I just ha another crash, but unlike most of the crashes get, this one actually generated a crash report. It happened when I tried to open a file. had two cyberduck browser windows open at the time; each had a separate ftp connection open on different servers. Crash Report: Date/Time: 2008-08-14 08:34:33.262 -0400 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Application Specific Information: Java information: Current thread (0x01a01310): JavaThread "main" [_thread_in_native, id=-1601007712] VM state:not at safepoint (normal execution) Heap Virtual Machine arguments: Thread 0 Crashed: Thread 1: Thread 2: Thread 3: Thread 4: Thread 5: Thread 6: Thread 7: Thread 8: Thread 9: Thread 10: Thread 11: Thread 12: Thread 13: Thread 14: Thread 15: Thread 16: Thread 17: Thread 18: Thread 19: Thread 20: Thread 0 crashed with X86 Thread State (32-bit): Binary Images: |
confirmed. in fact, doing just about anything will make this app crash. this has been true for the past half dozen releases. currently using version Version 3.0.2 (4166) on a mac min and a macbook, both leopard. the app is almost unusable these days. it even crashed when i went to look at the about info! |
here's a dump: Process: Cyberduck [31050] Date/Time: 2008-08-14 19:33:02.600 -0700 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Application Specific Information: Java information: Current thread (0x01a01300): JavaThread "main" [_thread_in_native, id=-1610334304] VM state:not at safepoint (normal execution) Heap Virtual Machine arguments: Thread 0 Crashed: Thread 1: Thread 2: Thread 3: Thread 4: Thread 5: Thread 6: Thread 7: Thread 8: Thread 9: Thread 10: Thread 11: Thread 12: Thread 13: Thread 14: Thread 15: Thread 16: Thread 17: Thread 18: Thread 0 crashed with X86 Thread State (32-bit): Binary Images: |
I got so fed up with this, I downgraded to 2.8.5, and I haven't had a single crash since. |
I also had to move to 2.8.5. The 4166 build has been the worst yet. It was crashing with crash reports and also doing the disappearing thing where no report is generated. I will keep trying new versions as possible, but the 3.0.x isn't ready for the real world. I have had files disappear, things say they uploaded/saved successfully but remain unchanged on the server, crashes, etc. Sorry for the bad news :-( |
Also have problems, that cyberduck crashes after editing files or pressing the disconnect button. sometimes no bug report is shown, don't know why. If the next bug report appears, then I will post the content. |
sorry... forgotten my email Also have problems, that cyberduck crashes after editing files or pressing the disconnect button. sometimes no bug report is shown, don't know why. If the next bug report appears, then I will post the content. |
Opened a connection, double clicked a folder and cyberduck crashed: Process: Cyberduck [7607] Date/Time: 2008-08-25 14:18:28.786 +0200 Exception Type: EXC_BAD_ACCESS (SIGBUS) Application Specific Information: Java information: Current thread (0x01a01310): JavaThread "main" [_thread_in_native, id=-1601380448] VM state:not at safepoint (normal execution) Heap Virtual Machine arguments: Thread 0 Crashed: Thread 1: Thread 2: Thread 3: Thread 4: Thread 5: Thread 6: Thread 7: Thread 8: Thread 9: Thread 10: Thread 11: Thread 12: Thread 13: Thread 14: 7 libjvm.dylib 0x00416655 0x3b9000 + 382549 Thread 15: Thread 0 crashed with X86 Thread State (32-bit): Binary Images: |
Guys, can we please not post these crash reports directly into the comment thread? It's pretty worthless to most of us and makes it impossible to read the actual reports. You can upload them as attatchments and just mention the attatchment in your post, much cleaner and totally effective. |
The error came after this procedure: Attachement: |
one more report here, using Cyberduck with TextMate to edit remote files. This bug appears for me in one case without fail: Open a connection via SFTP. Sometimes I use the mouse for some of those steps but the crash never seems to occur until Cyberduck regains focus. Cyberduck is the best FTP app out there, free or payware. It destroys Transmit and ForkLift. Please fix this bug so I can use it again :) |
Can conform your comment. Exactly the same for me. |
Version 3.0.2 (4173) Still crashes when closing a file in Smultron its like clock work...every time I close a file in Smultron, Cyberduck crashes. I have tried resetting the app and also re-downloading and re-installing it. My computer: |
Fixed in a415a62. Please try the latest nightly build from (http://update.cyberduck.ch/nightly). |
I've had cyberduck crash multiple times recently, and they seem almost random occurances; however, it's almost always when the focus is coming back onto cyberduck from my text-editor (Smultron). Soon as I switch back, it pauses for about 2 seconds, and then dies. Sometimes I get a crash report(Sent to Apple) pop-up, and sometimes, it's just gone and there's no message.
I've had this happened off an on ever since upgrading to Leopard and Cyberduck 3.x I never once had a problem on the older version. I've used all the newest nightlies, and none of them seem to help. They all seem to crash randomly when I return the focus to cyberduck.
These crashes just about render cyberduck useless, because I browse to my file, open it up, make a change and switch back to cyberduck, and it all crashes, and I have to open back up to the server and browse to the next file. It's very frustrating.
I love cyberduck, and I will continue to use it and suppport it, but this is ridiculous.
Here's the output from the crash report if it helps.
Attachments
SIGSEGV.txt
(39.5 KiB)cyberduck-crash-report-jeremyclarke.txt
(37.7 KiB)cyberduck_error.txt
(37.3 KiB)The text was updated successfully, but these errors were encountered: