[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-bugs
Subject: [Wireshark-bugs] [Bug 7722] Wireshark crashes when changing configuration profiles
From: bugzilla-daemon () wireshark ! org
Date: 2012-12-29 4:02:29
Message-ID: bug-7722-15-Hcfmx2yVyI () https ! bugs ! wireshark ! org/bugzilla/
[Download RAW message or body]
--1356753751.687e12.6490
Date: Fri, 28 Dec 2012 20:02:31 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.wireshark.org/bugzilla/show_bug.cgi?idw22
--- Comment #2 from Jim Aragon <Jim@agdatasystems.com> ---
This is to confirm that as of Version 1.9.0-SVN-46832, Wireshark still crashes
when changing configuration profiles, but the behavior is slightly different
than I originally reported.
On my Windows Vista PC, if I change the configuration profile twice, Wireshark
will close with no error message. It no longer displays the "Wireshark has
stopped working" message.
On this same PC, the PortableApps version of Wireshark will also close without
any message, but it sometimes takes three or four configuration profile
changes, instead of two.
The 64-bit version, running on my Windows 7 laptop, continues to display the
"Wireshark has stopped working" message, and the number of profile changes
required to trigger the error seems to be variable. Usually the error occurs
after three or four changes, but on one occasion it took six changes.
--
You are receiving this mail because:
You are watching all bug changes.
--1356753751.687e12.6490
Date: Fri, 28 Dec 2012 20:02:31 -0800
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<base href="https://bugs.wireshark.org/bugzilla/" />
<style>
body, th, td {
font-size: 12px;
font-family: Arial, Helvetica, sans-serif; }
p, pre { margin-top: 1em; }
pre {
font-family: Bitstream Vera Sans Mono, Consolas, Lucida Console, \
monospace; white-space: pre-wrap;
}
table { border: 0; border-spacing: 0; border-collapse: collapse; }
th, td {
padding: 0.25em;
padding-left: 0.5em;
padding-right: 0.5em;
}
th { background: rgb(240, 240, 240); }
th.th_top { border-bottom: 1px solid rgb(116, 126, 147); }
th.th_left { border-right: 1px solid rgb(116, 126, 147); }
td.removed { background-color: #ffcccc; }
td.added { background-color: #e4ffc7; }
</style>
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED --- - Wireshark crashes when changing configuration profiles"
href="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7722#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED --- - Wireshark crashes when changing configuration profiles"
href="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7722">bug 7722</a>
from <span class="vcard"><a class="email" \
href="mailto:Jim@agdatasystems.com" title="Jim Aragon \
<Jim@agdatasystems.com>"> <span class="fn">Jim Aragon</span></a> \
</span></b>
<pre>This is to confirm that as of Version 1.9.0-SVN-46832, Wireshark still \
crashes when changing configuration profiles, but the behavior is slightly \
different than I originally reported.
On my Windows Vista PC, if I change the configuration profile twice, Wireshark
will close with no error message. It no longer displays the "Wireshark has
stopped working" message.
On this same PC, the PortableApps version of Wireshark will also close without
any message, but it sometimes takes three or four configuration profile
changes, instead of two.
The 64-bit version, running on my Windows 7 laptop, continues to display the
"Wireshark has stopped working" message, and the number of profile changes
required to trigger the error seems to be variable. Usually the error occurs
after three or four changes, but on one occasion it took six changes.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>
--1356753751.687e12.6490--
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic