After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 213207 - compose (message) window takes forever to open
compose (message) window takes forever to open
Status: RESOLVED FIXED
Product: GtkHtml
Classification: Other
Component: html-editor-control
unspecified
Other All
: Normal normal
: Future
Assigned To: Larry Ewing
Evolution QA team
: 214694 (view as bug list)
Depends on:
Blocks: 216098
 
 
Reported: 2001-10-22 19:42 UTC by kliermanm
Modified: 2003-04-05 20:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kliermanm 2001-10-22 19:42:31 UTC
Package: Evolution
Priority: Normal
Version: 0.15
Synopsis: compose (message) window takes forever to open
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
on both my computers, evolution runs somewhat slow.... however, the
compose window takes especially long to open.  Can anything be done to
speed this up?  If nothing else, maybe preopen a hidden compose window
then just show it when you ask to compose a message?



Unknown reporter: kliermanm@bigfoot.com, changed to bugbuddy-import@ximian.com.

Comment 1 Luis Villa 2001-10-26 02:11:23 UTC
Something really good to look at for 1.1/1.2 if possible. 
Comment 2 Luis Villa 2001-11-26 17:01:39 UTC
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be
moving a large number of bugs around in the bugzilla. You can just
search on 'body contains' 'Because of the decision to remap' and mark
all as read. Please direct all questions about this change to
evolution@ximian.com, not the bug.
Luis
Comment 3 Luis Villa 2001-11-27 19:19:23 UTC
1) this is gtkhtml suckage, isn't it. 
2) Is there any way we can profile this in a 1.2 timeframe? It's
probably the worst user interaction performance issue we have.
Comment 4 Radek Doulik 2001-11-27 20:14:55 UTC
actually no, this is bonobo issue.
Comment 5 Luis Villa 2001-12-04 19:19:55 UTC
Whether or not it's bonobo it's bad and ought to be looked at.
Comment 6 Larry Ewing 2001-12-04 19:46:56 UTC
It is almost certainly bonobo.  On irc you were saying it got slower
recently, if that is true can you give us a time frame?  Hmmm I did
add a lot of menu items at some point, that probably made it worse.

About the only thing I can think of to make it seem faster is make evo
start a composer an start time and keep it hidden.  Then when the user
clicks it should be faster.  But that is really sick. Really really sick.
Comment 7 Luis Villa 2001-12-07 15:04:38 UTC
Unfortunately, I don't recall a date. :( And ettore suggested in the
meeting that it could have been related to more bonobo stuff starting
up without a bonobo change (I don't think he mentioned menus, but that
may have been what he was referring too.) So... ugh. I'd like to leave
this on the 1.2 radar for the time being because it is the most
glaring performance issue we have left. If we can't solve it, we
should at least have a whirly icon or message in the status bar to
indicate work is being done.
Comment 8 Luis Villa 2001-12-13 20:56:39 UTC
*** bug 214694 has been marked as a duplicate of this bug. ***
Comment 9 Michael Meeks 2002-01-24 09:24:23 UTC
Well it's relatively possible to speed the thing up. I imagine the
problem is that each time we re-exec gtkhtml, so one pragmatic way to
do this is to keep a copy of gtkhtml in the background that you arn't
using - that will speed up new window creation.

Another way to do it is to hold a reference on the factory - sadly in
Gnome 1.4 that's not so easy to do.

Yet another way is to ensure that the gtkhtml component doesn't quit
and de-register when it looses it's last window, but instead waits for
(perhaps a minute) and then de-registers itself.

That should provide a nice speedup with no (vicious) lifecycle
ramifications.
Comment 10 Ettore Perazzoli 2002-01-25 20:48:40 UTC
This should be almost fixed with the latest Bonobo.  Removing the
"feature" keyword.
Comment 11 kliermanm 2002-01-28 20:24:05 UTC
i just installed bonobo 1.0.19 and am not seeing an improvement.... is
this the version you are refering to, or a CVS version?
Comment 12 Michael Meeks 2002-01-29 09:54:30 UTC
Hi Lad, I think Ettore is wrong - most of the existing slowness with
opening gtkhtml is most likely activation overhead - execing the
process and then when you've composed your mail and do a new one
re-execing a new process - very wasteful. As suggested above we need
to hold a reference on something and have a timeout.
Comment 13 Larry Ewing 2003-04-05 20:15:38 UTC
The editor is now a shlib by default and composer startup is pretty
fast, closing this bug.