GNOME Bugzilla – Bug 334041
Properties page creation slows nautilus down
Last modified: 2006-03-14 13:49:55 UTC
"libtotem-properties-page.so, a Nautilus extension, 0.3 seconds. It initializes GStreamer on startup (!). Can it delay the initialization of GStreamer until Nautilus makes the first real call into any of the extension's methods?" Yep, we're calling gst_init() in nautilus_module_initialize(). Bleh, let's init it when we create the first page instead...
Created attachment 60986 [details] [review] totem-init-backend-later.patch That should work. Any takers for testing?
Works for me (TM)
Works great (Gentoo, totem-2.13.92 from gnome-experimental).
Works fine here as well. Gentoo AMD64, totem-2.13.92 (from Break My Gentoo).
2006-03-11 Bastien Nocera <hadess@hadess.net> * src/totem-properties-main.c: (totem_properties_get_pages), (nautilus_module_initialize): only initialise the backend when we create the first page, making nautilus startup slightly faster with the GStreamer backend (Closes: #334041)
i haven't have the chance to try this patch, however i think it is moving the problem from one place to another, as the first time that you click on the properties of a multimedia file the dialog will take a "long" time to be shown. How about initializing gstreamer in an idle loop or something like that?
Thanks for the patch, Bastien! I'm taking a new timing run. (In reply to comment #6) > i haven't have the chance to try this patch, however i think it is moving the > problem from one place to another, as the first time that you click on the > properties of a multimedia file the dialog will take a "long" time to be shown. > > How about initializing gstreamer in an idle loop or something like that? ... the we would be eating time in the idle loop. You have to do the initialization *somewhere*, after all :) In any case, first let's see if it is a problem to initialize gstreamer when the property page is brought up.