Sent that last one too fast... On Wed, Oct 10, 2012 at 3:19 PM, Evan Huus <[email protected]> wrote: > On Wed, Oct 10, 2012 at 3:18 PM, Jakub Zawadzki > <[email protected]> wrote: >> On Wed, Oct 10, 2012 at 12:19:42PM -0400, Evan Huus wrote: >>> At this point I want to just revert the whole recent set of emem >>> changes *and* the ref-counting. (...) >>> I don't have access to a commit-capable machine again until tomorrow >>> evening, so if somebody else wants to take care of it that would be >>> appreciated. >> >> Done.
Thanks. >>> If it fixes the original crasher and doesn't cause any other problems, go >>> ahead and commit it. >> >> I can't reproduce bug #5284 with GTK+ 2.24.4, I'll try wireshark-1.8.x. > > 1.8 still has ref-counting, so you won't see it there. Last time I > looked at it (April) I could reproduce, so if you still can't I'll > give it a try. I won't be able to try it until Thursday evening, so if you can't reproduce by then I'll give it a shot. Fortunately 1.8 doesn't have most of the leak that the ref-counting caused, since that was dependent on some other changes, so none of the recent mess affects a released version. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
