https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12804
--- Comment #9 from Patrick <patrick.sulliv...@emc.com> --- (In reply to Peter Wu from comment #6) > You mentioned that the memory grows after some time, does this happen during > live captures? Do you have any interaction? We could optimize a bit if your > scenario needs it. The Wireshark process is 6GB (I know I just wrote 10 GB on the attachments up there, but I'm still drinking coffee). Its not a big problem for my workflow as I normally use wireshark for analysis of file sharing protocols and rarely if ever for https traffic. If you guys need to triage its not a problem, its an edge case where someone would have a ssl key log file that big and I can work around by just removing it or saving the ssl key log files individually. I'm just glad you knew that it would be the keylog file. Might be an interesting issue though. -- 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://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
