Comment # 3
on bug 9026
from Evan Huus
(In reply to comment #2)
> Evan, what's up with the assertion message here? That confused me about
> this bug: I wasn't sure if it was really out of memory or if wmem was having
> a bad day.
It's just a side-effect of the way we handle this exception. Wmem expects there
to be no packet in-scope when the file closes, but in this exception handler we
close the file without exiting the packet scope (tshark.c:1957). I'm not sure
we can assume that there *is* a packet in scope when this exception occurs...
You are receiving this mail because:
- You are watching all bug changes.