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

Memory usage #9878

Closed
cyberduck opened this issue Mar 11, 2017 · 12 comments
Closed

Memory usage #9878

cyberduck opened this issue Mar 11, 2017 · 12 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 11, 2017

548dbe8 created the issue

I am using newest (5.3.9) version of Cyberduck on OSX 10.12.3. After launch it uses about 180 MB of memory. The memory usage grows within 10 or so seconds to about 950 MB (no user input of connection to any server needed). Then over the next minute it grows up to 1.15 GB. The memory growth is not accompanied by any user input. This behaviour existed for at least one or two years. Is there a log I can attach? The Log Drawer is empty. Is there a Log I could attach?


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 12, 2017

@dkocher commented

We recently fixed two memory issues in edd4570 and b4583df. Can you check the current snapshot build available. Navigate to Cyberduck → Preferences… → Update → Snapshot Builds to update.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 12, 2017

@dkocher commented

Possible regression from 45a5364.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 12, 2017

@dkocher commented

#9869 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 12, 2017

@dkocher commented

#9592 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 13, 2017

1d5c09d commented

I just compared 5.3.9 to latest 6.0 snapshot - I'm seeing pretty much the same huge memory usage as the original poster. I just launched Cyberduck (I have just about 50 bookmarks), opened & closed Prefs & Transfers windows several times, and am seeing memory use upwards of 800 megs, either version (slightly less in 6.0 snapshot than 5.3.9); see attached Activity Monitor screenshots. Also on 10.12.3.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 13, 2017

@dkocher commented

In 980182f.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 13, 2017

@dkocher commented

Switch to G1 Garbage Collector in d7fb65c.

Getting Started with the G1 Garbage Collector

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 13, 2017

@dkocher commented

Collect garbage after background task in 8cd5d09.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 14, 2017

548dbe8 commented

As far as I am concerned the problem is not fixed. After the update was downloaded I have updated to a daily snapshot and the program behaves exactly the same way as before. Current version unmber is 23732

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2017

@dkocher commented

Please make sure the build is 23761 or newer.

Loading

@cyberduck cyberduck closed this Apr 3, 2017
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2017

548dbe8 commented

Replying to [comment:11 dkocher]:

Please make sure the build is 23761 or newer.

It is 23803.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2017

548dbe8 commented

Replying to [comment:11 dkocher]:

Please make sure the build is 23761 or newer.

It is 23803 and the described behaviour still happens.

Loading

@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