Hi, This is my first real post to this list so a quick introduction is probably appropriate: My background is extensive Unix system and network administration in a university software engineering environment. I have broad and varied programming skills but not really an expert. I can work with most parts of the standard Unix tool chain etc. I've spent many years analysing and fixing software bugs in large packages etc (but none as big as this one - whew!).
I'm looking for a little help in locating a specific confirmed 'bug' in OOo: http://qa.openoffice.org/issues/show_bug.cgi?id=61228 'Large forms are very slow to open' In brief, I have a form with several hundred controls on it. The time to open the form increases 'exponentially' with the number of controls (roughly). My form takes 400 seconds to open. If possible, I would like some broad hints where to start looking. So far: I've checked out the release 2.0.1 revision from CVS (for a known stable rev) and have built and installed it. I'm now at the point of starting to profile. I've run strace and seen that only a relatively small amount of the time is spent in system calls. There are no obviously excessive numbers of system calls. I've built and run the writer project with RTL logging turned on to check that I understand the profiling process described on the web site, but only with the existing trace macros in the code. This seems to generate fairly minimal output. I expect to have to add trace calls and rebuild fairly often. Would I be better off just building the whole package with -DTIMELOG initially? One of the clues I have is that the entire OOo event loop appears to stall during the open - all OOo document windows stall. Is this typical? Does this suggest any specific areas of the code? What kind of things are able to stop the entire OOo event loop? Thanks. Ross Johnson --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
