Wireshark-bugs: [Wireshark-bugs] [Bug 9033] wmem assertion after changing preferences before loa
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 12 Aug 2013 23:45:43 +0000

changed bug 9033

What Removed Added
Status UNCONFIRMED CONFIRMED
CC   darkjames-ws@darkjames.pl, eapache@gmail.com
Ever confirmed   1

Comment # 1 on bug 9033 from 
Applying the prefs is triggering rescan_packets which is triggering wmem to
enter file scope.

#0  wmem_enter_file_scope () at wmem_scopes.c:99
#1  0x00007ffff4e025be in init_dissection () at packet.c:186
#2  0x00007ffff4df6b63 in epan_new () at epan.c:146
#3  0x0000000000431eb7 in ws_epan_new (cf=0x81d980 <cfile>) at file.c:339
#4  rescan_packets (cf=cf@entry=0x81d980 <cfile>, action=""
"Reprocessing", action_item=action_item@entry=0x57c6e5 "all packets", 
    redissect=redissect@entry=1) at file.c:1873
#5  0x00000000004321b4 in cf_redissect_packets (cf=cf@entry=0x81d980 <cfile>)
at file.c:1734
#6  0x0000000000445ece in redissect_packets () at main.c:3892
#7  0x000000000045bbf5 in prefs_main_ok_cb (ok_bt=<optimized out>,
parent_w=0x1e05ec0) at prefs_dlg.c:1478

There are probably two issues here:
- rescan_packets should bail because there is no file open
- if it doesn't bail, it should clean up the epan it creates so that wmem
leaves file scope

CCing Jakub; since this doesn't happen in 1.10 I suspect his epan_new changes
triggered this.

You are receiving this mail because:
  • You are watching all bug changes.