Wireshark mailing list archives
Re: qtshark startup time ~1 minute just printing messages
From: Evan Huus <eapache () gmail com>
Date: Mon, 9 Sep 2013 21:08:59 -0400
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 <eapache () gmail com> wrote:
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, Evan Huus <eapache () gmail com> wrote:On Mon, Sep 9, 2013 at 6:48 PM, Gerald Combs <gerald () wireshark org>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 Imaximizethe qtshark window immediately upon startup then the splash seems todo afull-window redraw for every change, and takes a significantly longer-than-usual amount of time to finish.Ah, that explains that last time I got annoyed by this it was more like 1,75 minutes. The window was larger.What happens if you disable antialiasing in the overlay or set its opacity to 1.0? I can't duplicate this (to any appreciable level, at least) on any of my test machines.No change - the splash is marginally faster in general, but it still slows down substantially when the window size is changed. I suspect it's some condition that is accidentally disabling the "Only update every splash_register_freq milliseconds" check, I will try and debug further.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: qtshark startup time ~1 minute just printing messages, (continued)
- Re: qtshark startup time ~1 minute just printing messages Gerald Combs (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Gerald Combs (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Joerg Mayer (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Joerg Mayer (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Gerald Combs (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Gerald Combs (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Joerg Mayer (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 10)
- Re: qtshark startup time ~1 minute just printing messages Gerald Combs (Sep 10)
- Re: qtshark startup time ~1 minute just printing messages Joerg Mayer (Sep 11)
- Re: qtshark startup time ~1 minute just printing messages Evan Huus (Sep 09)
- Re: qtshark startup time ~1 minute just printing messages Gerald Combs (Sep 09)