https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
Gerald Combs changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #22 from Gerald Combs ---
(In reply to David Eichar from comment #21)
> I just tried "net stop npf". After several seconds the response was:
> "The NetGroup Packet Filter Driver service could not be stopped."
> Note, this is hap
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
David Eichar changed:
What|Removed |Added
CC||d...@att.net
--- Comment #21 from D
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #20 from Gerrit Code Review ---
Change 26448 merged by Anders Broman:
Windows: Always assign newly-created processes to our job.
https://code.wireshark.org/review/26448
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #19 from Gerald Combs ---
The original issue should be fixed in
https://code.wireshark.org/review/#/c/26448/. It assigns dumpcap to a job
object[1] which terminates it when Wireshark, TShark, etc close. Job objects
won't magical
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #18 from Christopher Maynard ---
(In reply to clarkw from comment #8)
> See also: http://support.moonpoint.com/os/windows/processes/unkillable/
The link to
https://blogs.technet.microsoft.com/markrussinovich/2005/08/17/unkillab
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #17 from Pascal Quantin ---
Again please try to understand the difference between both cases. In the
initial issue there is no problem killing dumpcap manually. In your case, it's
dumpcap hanging that prevents Wireshark to prope
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #16 from clarkw ---
(In reply to Pascal Quantin from comment #14)
> Dumpcap uses system calls provided by WinPcap / Npcap to do the capture.
> So please reboot your machine before uninstalling WinPcap as a locked
> dumpcap could
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #15 from clarkw ---
(In reply to Pascal Quantin from comment #12)
> This bug is about Wireshark not stopping its child process dumpcap when it
> crashes, not about the fact that dumpcap cannot be stopped.
I hit the bug when I w
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #14 from Pascal Quantin ---
Dumpcap uses system calls provided by WinPcap / Npcap to do the capture.
So please reboot your machine before uninstalling WinPcap as a locked dumpcap
could prevent a proper uninstallation.
--
You a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #12 from Pascal Quantin ---
This bug is about Wireshark not stopping its child process dumpcap when it
crashes, not about the fact that dumpcap cannot be stopped.
Please try with Npcap. If it still fails, please open a dedicated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #13 from clarkw ---
(In reply to Pascal Quantin from comment #10)
> One possible solution (worth trying) is to remove WinPcap and instead
> install Npcap and see if you reproduce the issue.
Just tried and WinPcap can be uninsta
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #11 from clarkw ---
(In reply to Pascal Quantin from comment #10)
> We got similar reports in the past due to WinPcap preventing dumpcap from
> stopping.
> One possible solution (worth trying) is to remove WinPcap and instead
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
Pascal Quantin changed:
What|Removed |Added
CC||pascal.quan...@gmail.com
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
clarkw changed:
What|Removed |Added
Priority|Medium |High
Severity|Normal
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
Alexis La Goutte changed:
What|Removed |Added
Priority|High|Medium
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
clarkw changed:
What|Removed |Added
Version|0.99.5 |2.4.5
OS|Windows XP
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
clarkw changed:
What|Removed |Added
Priority|Medium |High
Severity|Major
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #8 from clarkw ---
See also: http://support.moonpoint.com/os/windows/processes/unkillable/
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
clarkw changed:
What|Removed |Added
CC||dearv...@gmail.com
--- Comment #7 from cl
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
Sloven changed:
What|Removed |Added
CC||slov...@yandex.by
--- Comment #6 from Slo
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
Chris Maynard changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
Michael Mann changed:
What|Removed |Added
CC||mman...@netscape.net
--- Comment #5
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #4 from Chris Maynard 2011-09-21
09:35:18 PDT ---
Could any of the ideas offered at the following help us here?
http://stackoverflow.com/questions/284325/how-to-make-child-process-die-after-parent-exits
--
Configure bugmail:
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|Critical|Major
--- Comment #3 fro
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
--- Comment #2 from [EMAIL PROTECTED] 2007-05-16 13:01 GMT ---
Is dumpcap capable of checking that its related Wireshark instance is gone?
That would be the preferable way to do it. Imagine a platform with multiple
instances of w
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|Major |Critical
--
Configure bugma
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|memory accumulates after|dumpcap keeps running after
28 matches
Mail list logo
