https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5284
--- Comment #35 from Evan Huus <eapache@xxxxxxxxx> 2012-10-11 06:02:37 PDT ---
(In reply to comment #34)
> (In reply to comment #33)
> > 1.8 doesn't suffer from the same bug that makes ref-counting
> > a problem in trunk.
>
> Evan, we also have problem in 1.8.x
> From my old mail[1]:
> #v+
> You can reproduce it by loading some bigger files, and several times open
> expert
> or conversation window.
> #v-
> If you can't reproduce it I can prepare sample capture file, which allocated
> lot of ep_ memory.
>
> [1] http://www.wireshark.org/lists/wireshark-dev/201208/msg00128.html
Right, I forgot about that. Selecting other packets doesn't leak in 1.8, but
expert and conversation windows do.
> > Honestly, if we can figure out for sure why it seems
> > to be fixed in trunk then I'm happy leaving well enough alone
> > and just closing the bug.
>
> Even if it seems fixed, I think we also need to commit something like
> attachment #9334 [details].
Agreed. I'm fine with it going in trunk, and if nothing blows up after a few
days then back-porting it to 1.8.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
