Skip to content

Don't upload addresses as they appear #1600

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

Merged
merged 1 commit into from
Feb 5, 2020

Conversation

PeterSurda
Copy link
Member

  • attempt to fix Excessive memory usage #1598
  • seems to work
  • addresses won't be uploaded/announced anymore other than after connecting, Later I need to find out how to announce them without causing problems, but for the time disabling this seems an acceptable drawback

@PeterSurda PeterSurda requested a review from g1itch February 5, 2020 01:03
@PeterSurda PeterSurda force-pushed the addr-memleak-fix-1 branch 3 times, most recently from f35ffe2 to b9d5eda Compare February 5, 2020 01:56
@g1itch
Copy link
Collaborator

g1itch commented Feb 5, 2020

Why don't you just comment the line where the peers are put into addrQueue?

@PeterSurda
Copy link
Member Author

I suppose that's also an approach.

- attempt to fix Bitmessage#1598
- seems to work
- addresses won't be uploaded/announced anymore other than after connecting,
  Later I need to find out how to announce them without causing problems, but
  for the time disabling this seems an acceptable drawback
@PeterSurda
Copy link
Member Author

there you go

Copy link
Collaborator

@g1itch g1itch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My problem with this is that I cannot reproduce the memleak. mprof doesn't show a substantial memory usage growth. ~ 5 MB difference that I can see may be caused by different number of connections in different lunches.

@PeterSurda
Copy link
Member Author

PeterSurda commented Feb 5, 2020

I tested it on one of the bootstrap servers, you probably need many incoming connections and it still takes a couple of hours to trigger, even a day. Then the memory consumption starts growing until it fills up and swap starts thrashing. Now it's been running for about 2 days without any issues (with the fix).

@PeterSurda PeterSurda merged commit 11bec55 into Bitmessage:v0.6 Feb 5, 2020
@PeterSurda PeterSurda deleted the addr-memleak-fix-1 branch August 27, 2020 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Excessive memory usage
2 participants