Wireshark · Wireshark-dev: Re: [Wireshark-dev] slow startup caused by splash

Wireshark-dev: Re: [Wireshark-dev] slow startup caused by splash_update?

From: Jeremy Linton <jli@xxxxxxxxxxxxxxxxxx>

Date: Mon, 06 Apr 2009 14:24:21 -0500

Jeff Morriss wrote:

How about some other GTK2 application? My recollection is that GTK2 ispretty talkative (in terms of X traffic).

I just started gimp 2.6.2, its got a similar splash screen. It started in ~10 seconds. It is laggy like wireshark,which lends credence that something in gtk is being a little more chatty than emacs/xterm/etc. The gtk version is2.14.4, glib 2.18.2 (default for my SUSE 11.1 install).

References:
- [Wireshark-dev] slow startup caused by splash_update?
  - From: Jeremy Linton
- Re: [Wireshark-dev] slow startup caused by splash_update?
  - From: Jeff Morriss
- Re: [Wireshark-dev] slow startup caused by splash_update?
  - From: Jeremy Linton
- Re: [Wireshark-dev] slow startup caused by splash_update?
  - From: Jeff Morriss
- Re: [Wireshark-dev] slow startup caused by splash_update?
  - From: Jeremy Linton
- Re: [Wireshark-dev] slow startup caused by splash_update?
  - From: Jeff Morriss

Prev by Date: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86
Next by Date: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc
Previous by thread: Re: [Wireshark-dev] slow startup caused by splash_update?
Next by thread: Re: [Wireshark-dev] slow startup caused by splash_update?
Index(es):
- Date
- Thread