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

Jump to bottom

Win32Exception in WindowsFormsApplicationBase.WriteUrlToMemoryMappedFile #8420

Closed
cyberduck opened this issue Dec 11, 2014 · 9 comments
Closed

Win32Exception in WindowsFormsApplicationBase.WriteUrlToMemoryMappedFile #8420

cyberduck opened this issue Dec 11, 2014 · 9 comments
Labels
bug duplicate webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

338f034 created the issue

First off thank you for the awesome service. Everytime I use it, I can't believe how great it is, and how efficient my workflow is, especially when uploading media every week for my company. As of last friday Dec 5th, 2014, the program has been crashing when I upload pictures. It was working fine and as I got to the end of my workflow, each time I drag and drop content to be uploaded, it crashes, and prompts me to send a crash report. Seeing that I need the program on a weekly basis, I was wondering what the ticket reporting process is like, and what the best way is to gather the info you need? Thx again for the awesome work, and have a great day!

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please attach the crash report and any related output in the system.log (/Applications/Utilities/Console.app).

@cyberduck
Copy link
Collaborator Author

338f034 commented

Replying to [comment:1 dkocher]:

Please attach the crash report and any related output in the system.log (/Applications/Utilities/Console.app).
I use a windows machine with cyberduck, and that directory (/Applications/Utilities/Console.app) doesn't exist on windows. I believe that's a Mac file directory that you've sent. Where do I go for windows? Thx again in advance for the help!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please attach the file cyberduck.log in the application support directory.

@cyberduck
Copy link
Collaborator Author

338f034 commented

Replying to [comment:3 dkocher]:

Please attach the file cyberduck.log in the application support directory.

I've attached the crash log/report, and it's titled "635542564786882109.txt​". Thank you again for the prompt response and support. Have a great day!

@cyberduck
Copy link
Collaborator Author

338f034 commented

Replying to [comment:5 dkocher]:
I'm not sure if I understood the instructions correctly. You'd like me to change settings within the windows structure? If so, where? Or is that the error that's happening, which is preventing me from uploading media to my specified location? Thx!

@cyberduck
Copy link
Collaborator Author

338f034 commented

Hey! I just wanted to report back, and to thank you for the update. It seems to have fixed the crashing that I was experiencing last week. I loaded the program, and was able to upload media appropriately. There was a weird instance when I tried to download an entire folder with media in it, and that cause the program to crash. I restarted and tried to download the same folder again, and this time it worked like it should. Not sure why it crashed initially, but hopefully with the crash report included you may be able to see what caused the issue. Again, I'd like to thank you for the awesome work you do! Have a great day!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I suspect the root cause of all crashes is that your operating system is low on memory. Closing as duplicate for #6550.

@cyberduck
Copy link
Collaborator Author

338f034 commented

Replying to [comment:8 dkocher]:

I suspect the root cause of all crashes is that your operating system is low on memory. Closing as duplicate for #6550.
Alright thx! I'll see what I can do then with managing the low memory. Thx again for the help in troubleshooting, and fixing the bug!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8464 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.
Assignees
No one assigned
Labels
bug duplicate webdav WebDAV Protocol Implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck