-
Notifications
You must be signed in to change notification settings - Fork 366
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
New clients do not receive data in Web-Viewer mode after dropping old messages #5344
Comments
I also experience this behavior. I am running Also if I may say another thing I experienced which is related to the memory limit, is that --memory-limit does not take effect for web viewer client. It defaults to 2.3GB, not 100MB which I expected. I will create an issue for this separately if I have to, thank you! |
I now have a full native repro for this (no web-viewer involved at all). I think this is just another manifestation of #5531, in particular the problem is not that no data is received, but rather that If I'm right, we can definitely come up with a simple patch for this. |
Describe the bug
out.mp4
After a while, new clients fail to recieve data in server mode. This happens once the memory limit is reached and some data is dropped.
To Reproduce
Steps to reproduce the behavior:
Memory limit (954 MiB) exceeded. Dropping old log messages from the server. Clients connecting after this will not see the full history
, open a new tab to the same URL: http://localhost:9090?url=ws://localhost:9877Expected behavior
On the new tab, older logs are lost but new data is streamed in.
Desktop (please complete the following information):
Rerun version
rerun_py 0.14.0 [rustc 1.74.0 (79e9716c9 2023-11-13), LLVM 17.0.4] x86_64-pc-windows-msvc release-0.14.0 0c723a8, built 2024-02-28T14:53:55Z
Additional context
Also occurs in the Rust program, but a Python replication of the bug was included here for a minimal reproducible sample.
The text was updated successfully, but these errors were encountered: