https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5284
--- Comment #32 from Anders Broman <anders.broman@xxxxxxxxxxxx> 2012-10-11 01:36:33 PDT ---
(In reply to comment #31)
> (In reply to comment #30)
> > Created attachment 9334 [details]
> > Alternative patch for 1.8 branch
> >
> > Using trunk:
> > I can't reproduce the problem on r45450
> > (but I agree there's a problem)
> >
> > Using wireshark-1.8 branch:
> > I can reproduce with reverted edt ref counting.
> > I can't reproduce the problem with attached patch (patch based on comment #3
> > and #26)
> I am seeing exactly the same thing. Based on the original analysis by Eduard,
> my best guess is that this was fixed accidentally by the custom packet byte
> field, since it's no longer triggering the same GTK callbacks as the old one.
> I don't know if it will be possible to find a way to reproduce this
> consistently (or at all) now.
Would the best soulution be to backport the custom packet byte widget to not
let the code divert to much making mantenance harder?
--
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.
