Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On Tue, Sep 10, 2013 at 05:25:25PM -0700, Gerald Combs wrote: > I don't recall a lot of controversy when the splash screen + progress > bar was added in 2004. Why all the fuss now? Because this is the first time that I had time to conciously look at and think about it ;-> I've been hit by the bug

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On 9/9/13 9:58 PM, Joerg Mayer wrote: > Hello Evan, > > On Mon, Sep 09, 2013 at 09:08:59PM -0400, Evan Huus wrote: >> It should be fixed in r51914 (see the commit message for more details). >> Joerg, please let me know if it now works for you (or if you are in fact >> seeing a different bug). > >

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On 2013-09-10, at 12:58 AM, Joerg Mayer wrote: > Hello Evan, > > On Mon, Sep 09, 2013 at 09:08:59PM -0400, Evan Huus wrote: >> It should be fixed in r51914 (see the commit message for more details). >> Joerg, please let me know if it now works for you (or if you are in fact >> seeing a different

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

Hello Evan, On Mon, Sep 09, 2013 at 09:08:59PM -0400, Evan Huus wrote: > It should be fixed in r51914 (see the commit message for more details). > Joerg, please let me know if it now works for you (or if you are in fact > seeing a different bug). Fixed. Thanks! Now that it is working, the only

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

It should be fixed in r51914 (see the commit message for more details). Joerg, please let me know if it now works for you (or if you are in fact seeing a different bug). Evan On Mon, Sep 9, 2013 at 8:58 PM, Evan Huus wrote: > Got it, though I'm not sure the optimal fix - basically, the problem

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

Got it, though I'm not sure the optimal fix - basically, the problem is that when a Paint takes more than info_update_freq_ milliseconds then every single event causes a Paint (because just the last Paint took enough time to trigger the timer). I will dig further On Mon, Sep 9, 2013 at 8:47 PM, E

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On 9/9/13 5:47 PM, Evan Huus wrote: > On Mon, Sep 9, 2013 at 6:48 PM, Gerald Combs > wrote: > > On 9/9/13 3:18 PM, Joerg Mayer wrote: > > On Mon, Sep 09, 2013 at 05:38:27PM -0400, Evan Huus wrote: > >> This is actually quite reproducible (on my machine at

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On Mon, Sep 9, 2013 at 6:48 PM, Gerald Combs wrote: > On 9/9/13 3:18 PM, Joerg Mayer wrote: > > On Mon, Sep 09, 2013 at 05:38:27PM -0400, Evan Huus wrote: > >> This is actually quite reproducible (on my machine at least). If I > maximize > >> the qtshark window immediately upon startup then the s

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On 9/9/13 3:18 PM, Joerg Mayer wrote: > On Mon, Sep 09, 2013 at 05:38:27PM -0400, Evan Huus wrote: >> This is actually quite reproducible (on my machine at least). If I maximize >> the qtshark window immediately upon startup then the splash seems to do a >> full-window redraw for every change, and

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On Mon, Sep 09, 2013 at 05:38:27PM -0400, Evan Huus wrote: > This is actually quite reproducible (on my machine at least). If I maximize > the qtshark window immediately upon startup then the splash seems to do a > full-window redraw for every change, and takes a significantly > longer-than-usual a

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On Mon, Sep 09, 2013 at 02:02:51PM -0700, Gerald Combs wrote: > On 9/9/13 1:44 PM, Joerg Mayer wrote: > > printing the "registering" and "handing off" messages at qtshark > > startup takes about 1 minute on my system. Can this "feature" please > > be fixed? > > What happens if you change info_upda

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

This is actually quite reproducible (on my machine at least). If I maximize the qtshark window immediately upon startup then the splash seems to do a full-window redraw for every change, and takes a significantly longer-than-usual amount of time to finish. On Mon, Sep 9, 2013 at 5:30 PM, Evan Huu

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

I've noticed this behaviour sometimes when running locally - it seems to be related to resizing the window. I will see if I can reproduce reliably. On Mon, Sep 9, 2013 at 4:44 PM, Joerg Mayer wrote: > Hello, > > printing the "registering" and "handing off" messages at qtshark > startup takes abo

[Wireshark-dev] qtshark startup time ~1 minute just printing messages

Hello, printing the "registering" and "handing off" messages at qtshark startup takes about 1 minute on my system. Can this "feature" please be fixed? thanks Jörg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On 9/9/13 1:44 PM, Joerg Mayer wrote: > Hello, > > printing the "registering" and "handing off" messages at qtshark > startup takes about 1 minute on my system. Can this "feature" please > be fixed? What happens if you change info_update_freq_ in splash_overlay.cpp from 50 to 100 (or 1000)? _

Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages

On 9/9/13 2:02 PM, Gerald Combs wrote: > On 9/9/13 1:44 PM, Joerg Mayer wrote: >> Hello, >> >> printing the "registering" and "handing off" messages at qtshark >> startup takes about 1 minute on my system. Can this "feature" please >> be fixed? > > What happens if you change info_update_freq_ in s