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!
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!
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!
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!
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!