Wireshark
the world's foremost network protocol analyzer
Wireshark-dev: [Wireshark-dev] slow startup caused by splash_update?
From: Jeremy Linton <jli@xxxxxxxxxxxxxxxxxx>
Date: Fri, 03 Apr 2009 16:24:46 -0500
As a FYI:I have been having problems with startup time (> 1 minute) with a 1.1.2 version compiled from the source tar (suse 11). So I went looking and discovered the majority of the startup time in my situation was actually the splash screen updates.
I replaced the splash_update in the call to epan_init() (gtk/main.c) with a NULL, and that cut the startup time to less than a second. I found some other comments complaining about the number of plug-ins causing slow startups, but it looks like in my case its more a case of trying to update the progress bar on the splash screen causing slow startups than having hundreds of plug-ins.
- Follow-Ups:
- Re: [Wireshark-dev] slow startup caused by splash_update?
- From: Jeff Morriss
- Re: [Wireshark-dev] slow startup caused by splash_update?
- Prev by Date: [Wireshark-dev] Problem with libsmi and adding MIB files
- Next by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 27948: /trunk/epan/ /trunk/epan/: emem.c
- Previous by thread: [Wireshark-dev] Problem with libsmi and adding MIB files
- Next by thread: Re: [Wireshark-dev] slow startup caused by splash_update?
- Index(es):