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.

Sign up for GitHub

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

Jump to bottom

--lateral-all on large logs #58

Closed
LiamWakefield opened this issue Jan 26, 2022 · 2 comments
Closed

--lateral-all on large logs #58

LiamWakefield opened this issue Jan 26, 2022 · 2 comments
Assignees
@alexkornitzer
Labels
question Further information is requested

Comments

@LiamWakefield
Copy link

LiamWakefield commented Jan 26, 2022 •
edited

had a 200mb log which shows the 4624 when using "search" however doesn't when using "hunt".

is it an issue with log size?
@alexkornitzer alexkornitzer self-assigned this Jun 2, 2022
@alexkornitzer
Copy link
Contributor

Right so --lateral-all will enable aggregation of data which is generally memory intensive. My guess is that if you look at the exit code it will be due to OOM. There is a change though that with v2 the memory usage is smaller. If you are able to check any of these theories that would be great.

@alexkornitzer alexkornitzer added the question Further information is requested label Jun 7, 2022
@FranticTyping
Copy link
Collaborator

@LiamWakefield - I believe this issue should be fixed with Chainsaw v2. Could you please download the latest release and see if you experience the same issues we can re-open this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexkornitzer alexkornitzer

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexkornitzer @FranticTyping @LiamWakefield