[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#960036: inkscape takes 100% CPU when opening font combobox



>Indeed, that's considered a lot.  For comparison, I have 481 :)
it doesn't depend on the number of fonts, even if with more fonts it slows down a lot

>In theory, if you leave the program at it long enough (which effectively
>means you won't be able to use the system during that time...) it should
>finish and be able to generate all the previous.
after 5 minutes the program exits with this error:

This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 42137 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

>Also, that would be a one-time thing the first time you open the font selector.
yes, but it takes about 30 seconds to complete

>Also, if you manage to close the drop-down it should likewise "unfreeze".
I can't close the combobox because the desktop appears frozen

>Another workaround is to disable the generation of the font previews.
works: for now use this solution

>Could you please share this in the upstream bug I linked before, or
>would you prefer me to proxy the message?
you manage


Il giorno ven 8 mag 2020 alle ore 22:41 Mattia Rizzolo <mattia@debian.org> ha scritto:
Control: tag -1 -moreinfo
Control: forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/841
Control: severity -1 normal

On Fri, May 08, 2020 at 07:55:19PM +0200, Antonio wrote:
> >Could you please provide us:
> >    fc-list | wc -l
> 4083

Indeed, that's considered a lot.  For comparison, I have 481 :)

In theory, if you leave the program at it long enough (which effectively
means you won't be able to use the system during that time...) it should
finish and be able to generate all the previous.  Also, that would be a
one-time thing the first time you open the font selector.
Also, if you manage to close the drop-down it should likewise
"unfreeze".  Another workaround is to disable the generation of the font
previews.

See the above upstream bug about this.

I recommend you follow up directly in the upstream bug I posted above if
you have any other information. :)

--
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Reply to: