Wireshark-bugs: [Wireshark-bugs] [Bug 3270] New: freezes on start, uses 100% kernel cpu, cannot
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 21 Feb 2009 07:31:36 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3270

           Summary: freezes on start, uses 100% kernel cpu, cannot kill.
           Product: Wireshark
           Version: 1.0.6
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: Blocker
          Priority: High
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: quartz12h@xxxxxxxxx


Build Information:
I cannot provide such information, it won't start.
It is the 1.0.6 for windows. Just downloaded TODAY (feb. 21st 2009).

--
I used to use wireshark 1.0.0 in the past without problems.
In presence of sygate personal firewall and AVG antivirus.
Now it doesn't work. I installed the latest 1.0.6 and it still freezes on
start.
Process explorer show 100% cpu in kernel, and I cannot kill this task, I cannot
even shutdown the PC gracefully. I have to reset or power down!

Changes:

I recently removed a PPPoe stack because I now have a router.

I get the AVG updates but I installed it without the http scanner and without
the firewall (with special arguments to their setup.exe program, and it really
doesn't install any net interceptor).

I didn't changed any of the sygate firewall settings. It should not interfere
more nor less than before.

I also tuned my PC MTU from 1500 own to 1454 with TCP IP optimizer
(http://www.speedguide.net/downloads.php) and the receive window is 260176.
Dunno if that matters to you, but there it is. I can provide more abotu the tcp
ip stack if I can find it.

That's the only changes in this PC. Wireshark barely show the small splash
screen and that's it, doesn't even repaint it when frozen (clearly loops
infinitely without i/o of any kind).

Note that this is windows 2000 sp4, although, like I said, I used to run 1.0.0
without problems, so the OS isn't the sensitive part. I think the boot sequence
of wireshark isn't immune to the abscence of something my pc recently stopped
providing (or presence of something new...).


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.