Swar2424
Swar2424
Small correction here : I just got the same error with v2.3.0, with a 400 Mo .kcap file
I do the capture and replay on the same machine, but the issue only rises up with big files (i.e. over 300 Mo and 10 000 000 events). With smaller...
So I can't put the .kcap file here, since github doesn't support .kcap format for attachments. Do you have a way I could send it directly to you ?
Update : I got the same error WITHOUT any flags or filters. Maybe with my earlier tests I just wasn't waiting long enough to see this error. Just the command...
I can also confirm it isn't a performance issue : according to windows task manager, with a processor usage of 55 % and a RAM usage of 45 % (approximately),...
I uploaded 2 capture files on wetransfer that are unreplayable on my side, made with v2.3.0 I think (although the issue still remains for v2.4.0). You should receive the link...
I have narrowed it down a little, and it seems like it's only the RegSetValue events that pose an issue. When I try to filter those that have an int-type...
I have send you a kcap file that is unreplayable. Here's how I captured and replayed that file : PS C:\Users\Félix\Documents\Test2> fibratus capture "kevt.name = 'RegSetValue'" -o events.kcap ┌─────────────────────────────────┐ │...