https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13226
--- Comment #4 from Guy Harris <g...@alum.mit.edu> --- (In reply to Michael Mann from comment #3) > This test file has definitely been accused of being a memory hog, see bug > 13049. I didn't mark it a duplicate because it was definitely a different > call stack, but I can agree with the issue really just being running out of > memory. ...or running out of CPU time, as happened with this crash. -- You are receiving this mail because: You are watching all bug changes.
___________________________________________________________________________ Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
