Wireshark-bugs: [Wireshark-bugs] [Bug 5871] New: System lockup when a packet is viewed
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 28 Apr 2011 22:55:52 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5871

           Summary: System lockup when a packet is viewed
           Product: Wireshark
           Version: 1.4.5
          Platform: Other
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: temp636@xxxxxxxxxxxx


Created an attachment (id=6257)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6257)
This is the capture that I can hang Wireshark on my machine if I click on a
packet ( I think it is 13, but I am afraid to try it now as I may lose the
whole message I am sending ) 

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
I was capturing a transfer to "online-convert.com" to see what a file upload
looked like.  I sent them a 10K or so text file instead of a video file as
"upload file" for them to convert.  I wanted them to simply accept and trash
the file as nonsense, as I just wanted to see how the packets were formed to
upload files via HTTP form=file commands.

Anyway, I succeeded in locking up my system when I tried to view a packet... I
think it was packet#13 on the attached.

I snipped  the error window I got back.  On the computer, it would lock up and
CPU util would go to 100%.  It did not crash Windows itself, but it did require
that I close Wireshark.

This is what I got from Windows:

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:    AppHangB1
  Application Name:    wireshark.exe
  Application Version:    1.4.5.36650
  Application Timestamp:    4da8853a
  Hang Signature:    6de0
  Hang Type:    0
  OS Version:    6.1.7600.2.0.0.768.3
  Locale ID:    1033
  Additional Hang Signature 1:    6de0fbe75cf35635bee81d775eea645d
  Additional Hang Signature 2:    394e
  Additional Hang Signature 3:    394e6b708e23fd0db6a3e0b16af381ca
  Additional Hang Signature 4:    6de0
  Additional Hang Signature 5:    6de0fbe75cf35635bee81d775eea645d
  Additional Hang Signature 6:    394e
  Additional Hang Signature 7:    394e6b708e23fd0db6a3e0b16af381ca

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy
statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Attached is the capture I got.  It will hang Wireshark when one of the packets
is viewed.  I think it was packet 13.

Please take a look at it... maybe I did something wrong...I don't wanna rattle
cages over my ignorance over simple misusing of a wonderful tool.

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