Comment # 5
on bug 10972
from Jeff Morriss
Hmm I don't think it's capture size related: I just loaded a capture with 1.4
million packets and could "Analyze this association" or "Prepare filter" on an
association with 186,000 frames just fine (of course it took a while).
Wireshark did use quite a bit of memory in the process, of course (but I've no
shortage of that as long as I don't start any VMs up).
What exactly is the error you're getting? Is it possible Wireshark's running
out of memory?
You are receiving this mail because:
- You are watching all bug changes.
