Wireshark-bugs: [Wireshark-bugs] [Bug 7833] Visual C++ Runtime Library "...the application has r
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 15 Oct 2012 06:40:34 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7833

alonbi@xxxxxxxxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alonbi@xxxxxxxxxxxxxxxxxxx

--- Comment #10 from alonbi@xxxxxxxxxxxxxxxxxxx 2012-10-15 06:40:32 PDT ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > >  Have you tried the latest stable 1.8.3 version? 
> > > 
> > (Note comment #1 above ....)
> 
> Based on the original information provided, i.e.:
>     Version 1.6.11 (SVN Rev 45257 from /trunk-1.6)
>     Compiled (32-bit) ...
>     Running on 64-bit Windows 7 ...
> 
> it wasn't clear to me whether "the newest" version pertained to the 32-bit
> 1.8.3 or the 64-bit version.  It may not make any difference, but for clarity,
> it would be nice to know which version was actually tried.

Hi.

I hope this information will help... I had the same problem with the 1.8.1
version on a Windows 2008 R2 x64 virtual machine. You can see the error below:

Log Name:      Application
Source:        Application Error
Date:          15/10/2012 02:45:54
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EGECS01
Description:
Faulting application name: wireshark.exe, version: 1.8.1.43946, time stamp:
0x500dabed
Faulting module name: libglib-2.0-0.dll, version: 2.32.2.0, time stamp:
0x4faa7bfc
Exception code: 0x40000015
Fault offset: 0x000000000004fd12
Faulting process id: 0xb4c
Faulting application start time: 0x01cda9deaa883720
Faulting application path: C:\Program Files\Wireshark\wireshark.exe
Faulting module path: C:\Program Files\Wireshark\libglib-2.0-0.dll
Report Id: ac60a5b0-1661-11e2-9b67-00155d002501

When starting a new capture, I saw that the Wireshark process was consuming
~2MB memory per second. I tried the same capture with versions 1.8.3 and 1.6.11
- yet the memory consumption growth rate remained the same. I then retried the
capture with a tried and tested 1.6.5 release and the memory consumption growth
was much lower. For now, I'm staying with version 1.6.5.

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