Gloobus hangs on this extreme document

[Pierre Slamich]

I know the size is a bit large, but a Friend trying Gloobus told me that it takes somewhere between 7 to 8 seconds for OOo while it takes 10 to 12 seconds for Gloobus and then freezes.
It could be a nice test for memory leaks, optimisations, etc...

[Hugo Roy (hugoroy)]

Actually, once the document has already been runned with OOo, it gets faster (~5 seconds).
But no evolution for Gloobus, it still takes about 10 seconds (and then freezes, I have to kill it).

PS: This is not so much of an "extreme docuement" I think. There isn't anything but texts, pictures and different kinds of pages. No macro or anything special.

[BadChoice (guitarboy000)]

Can you tri it with last bzr version?
I think I solved the problem

[BadChoice (guitarboy000)]

Since we don't use another engine to load word and openoffice documents, the only way is first convert to PDF and then load the PDF so it takes a little longer

[zp (zekopeko-deactivatedaccount)]

Why aren't we using a dedicated engine for this? What are you using to
render it to PDF? If we can render it to PDF why can't we directly
display it without going Word->PDF->Gloobus?

On Mon, Jan 11, 2010 at 1:11 PM, BadChoice <email address hidden> wrote:
> Since we don't use another engine to load word and openoffice documents,
> the only way is first convert to PDF and then load the PDF so it takes a
> little longer
>
> ** Changed in: gloobus
>       Status: Confirmed => Fix Committed
>
> ** Changed in: gloobus-preview
>       Status: In Progress => Fix Committed
>
> --
> Gloobus hangs on this extreme document
> https://bugs.launchpad.net/bugs/484082
> You received this bug notification because you are a member of Gloobus
> Developers, which is the registrant for gloobus-preview.
>

[BadChoice (guitarboy000)]

Cause I don't know other engine to load those documents... I'm trying to find out how abiword load it, but the api is down..