[bugzilla-daemon@xxxxxxxxxxxxx]

Pascal Quantin changed bug 12501

What	Removed	Added
Status	INCOMPLETE	RESOLVED
Resolution	---	WORKSFORME

Comment # 22 on bug 12501 from Pascal Quantin

(In reply to Dinesh Babu Sadu from comment #21)
> Hi 
> Is there any fix for this issue in any of the upcoming Wireshark release. I
> am eagerly waiting for this as i am not able to run the tool for more long
> hours (>2 hrs) for performing live/remote capture analysis.
> 
> We have raised Q&A in Wireshark forum about the same.
> https://ask.wireshark.org/questions/53437/wireshark-204-crashes-on-windows-
> 10-in-live-capture-analysis-using-remote-capture
> 
> Thanks in advance.
> 
> - Regards
>   Dinesh Sadu.

Hi Dinesh,

nothing in your post suggests that you are facing the issue described here
(that was related to a giant SSL configuration file), so I'm putting the bug
back to its original state.
Wireshark is not designed for long capture run as you will always end with an
out of memory situation. Instead you should use dumpcap to perform the capture.
I suggest you to read
https://blog.packet-foo.com/2013/05/the-notorious-wireshark-out-of-memory-problem/
and
https://blog.wireshark.org/2014/07/to-infinity-and-beyond-capturing-forever-with-tshark/
for possible workarounds.

---

      You are receiving this mail because:

• You are watching all bug changes.