-
Notifications
You must be signed in to change notification settings - Fork 7
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
reduce memory consumption #150
Milestone
Comments
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
ChunkListView exploits ListView features and enables LogoRRR to handle bigger log files as well
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
rladstaetter
added a commit
that referenced
this issue
Nov 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a user, I want to work with "huge" log files (>100mb). LogoRRR should handle such files without much hassle; currently it consumes much memory and crashes sooner or later.
Of course, there will be a certain limit for the size of the log files; it is not scope of the ticket to reinvent the whole text file handling. But the most pressing problems should be addressed and fixed.
The most problematic code in this regard is
BlockView
and friends which needs very much memory and isn't optimised for off screen rendering - it renders always everything.The text was updated successfully, but these errors were encountered: