You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 21, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 21, 2021. It is now read-only.
@aseyfpour nevermind, I figured out a way to reproduce using other data.
The specific thing that triggers this is a resend containing a massive number of data points, but we shouldn't be crashing regardless, there's something in our system that's holding onto references longer than it should.
Until I figure out a fix, one workaround would be to use resend: { last: NUM_MESSAGES } or reduce the from/to range to something smaller.
@timoxley Sorry for being late, I've been testing this version. I repeated the test several times and everything is OK with this version and I received more than 100K messages each time, but something has changed in the test environment. When I reported the issue, I received 60K messages in less than 10 minutes, but now it takes more than 3 hours to reach this amount (every time). I guess Streamr network speed is slower than before, so maybe my tests are not valid.
Activity
timoxley commentedon Mar 23, 2021
@aseyfpour thanks for the report. There may be a memory leak, I will investigate.
How long?
Roughly how many messages do you have and what kind of content is in them? Can you post some example messages?
timoxley commentedon Mar 23, 2021
@aseyfpour specifically, does the script above cause the error for you, exactly as-is, with the only change being adding of the
privateKey?aseyfpour commentedon Mar 24, 2021
After about 60K message.
Sample data:
aseyfpour commentedon Mar 24, 2021
Yes, I tested with this script twice before I submit this issue. Both times this problem occurred.
timoxley commentedon Mar 24, 2021
@aseyfpour
Can you add me as a subscriber to your stream so I can debug it?
0x58aE1e118Cd893a0Af51311AB486ce4968be79b6+buttonget+subscribepermissionstimoxley commentedon Mar 24, 2021
@aseyfpour nevermind, I figured out a way to reproduce using other data.
The specific thing that triggers this is a resend containing a massive number of data points, but we shouldn't be crashing regardless, there's something in our system that's holding onto references longer than it should.
Until I figure out a fix, one workaround would be to use
resend: { last: NUM_MESSAGES }or reduce thefrom/torange to something smaller.timoxley commentedon Mar 25, 2021
@aseyfpour can you please try again using
streamr-client@5.2.0-betaand let me know how it goes?aseyfpour commentedon Mar 27, 2021
@timoxley Sorry for being late, I've been testing this version. I repeated the test several times and everything is OK with this version and I received more than 100K messages each time, but something has changed in the test environment. When I reported the issue, I received 60K messages in less than 10 minutes, but now it takes more than 3 hours to reach this amount (every time). I guess Streamr network speed is slower than before, so maybe my tests are not valid.
aseyfpour commentedon Mar 29, 2021
I test it again today, It fetches more than 90K messages in less than 20 minutes. I think the problem is solved.
Thanks to @timoxley
timoxley commentedon Apr 1, 2021
🥳