-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
very slow start #16
Comments
I just tested Tartube (for the first time) on an Intel Celeron N4000 @1.10GHz, and the start time was 1.5 seconds. I have seen start times of about 30 seconds, but only when a lot of other things are happening. |
My laptop was mostly idle, except firefox (but it used something like 10% of the CPU). I tried to start gimp, which was faster than tartube. When I start tartube, the CPU usage stays low, during and after the start. |
I tested v1.1.0 on a fresh install of Debian, using an ancient laptop. The startup time was 3 seconds, which is what I expected. I'm not sure what might cause a 30-second setup time, but presumably the cause is deep within the Gtk/pygobject code somewhere. This could be tested by turning on the debug messages in the ../lib/mainapp.py file. In v1.1.0, it's line 67. You would change:
...to:
...and then run Tartube from a terminal window, so you can see the debug messages. The first message should read:
If there is a 30-second delay before that, then I have no idea how to fix it. |
I tried this, the 30-second delay is still here. It occurs between |
(as a side note, I would probably be better to read DEBUG_FUNC_FLAG from a DEBUG environment variable) |
I added DEBUG_FUNC_FLAG because I was having a lot of issues with Gtk. Those issues are now solved, so I will probably remove DEBUG_FUNC_FLAG soon. This test script is structurally the same as Tartube. Do you see a delay when you run it?
|
Yes, I see the delay on this program, too. It occurs between
|
|
What happens when you remove the menu action?
|
The same. As I said, Gtk.Application.do_startup(self) is the culprit |
OK, I think I found the problem: it was related to a dbus thing. I'm starting my window manager (xmonad) with startx, and I didn't source /etc/X11/Xsession.d/.* scripts. Something with dbus was starting each time I opened tartube, implying a ~30s delay. You didn't see it because gnome/whatever was starting the dbus thing for you... So, sorry, it was a problem on my part. It's the first time in many years it happens to me, though... Maybe it will happen to someone else using a minimal window manager someday! If it does, source the /etc/X11/Xsession.d/.* scripts in your .xinitrc :) |
I takes around 30s to start tartube on my laptop. Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz is not the latest cpu but a small program like this should still start faster...
The text was updated successfully, but these errors were encountered: