Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Crash when restarting capture.

From: Evan Huus <eapache@xxxxxxxxx>
Date: Fri, 8 Mar 2013 12:54:08 -0500
Should be fixed in r48193, and if not then I've cut that code path in
r48194 anyways.

On Fri, Mar 8, 2013 at 10:54 AM, Evan Huus <eapache@xxxxxxxxx> wrote:
> I will investigate.
>
> On Fri, Mar 8, 2013 at 10:30 AM, Anders Broman
> <anders.broman@xxxxxxxxxxxx> wrote:
>> Hi,
>>
>> During heavy traffic the following procedure is followed.
>>
>> -          Capture with wirsehark, don’t update packets in real time no auto
>> scrolling.
>>
>> -          Stop capture, wait while packets are read.
>>
>> -          Start new capture, stop capture.
>>
>> -          Once all packets are read(?) Wireshark crashes.
>>
>>
>>
>> (wireshark:25209): GLib-CRITICAL **: g_array_free: assertion `array' failed
>>
>>
>>
>> (wireshark:25209): GLib-CRITICAL **: g_array_free: assertion `array' failed
>>
>> **
>>
>> ERROR:wmem_allocator_block.c:341:wmem_block_split_free_chunk: assertion
>> failed: (!chunk->used)
>>
>>
>>
>> [1]+  Aborted                 (core dumped) wireshark
>>
>>
>>
>> The Glib warnings  is always there…, the wmem crash is the interesting bit.
>> Not sure if heavy traffic is needed.
>>
>> Regards
>>
>> Anders
>>
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>> Archives:    http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe