Bug#960036: inkscape takes 100% CPU when opening font combobox
Other infos: - if performed under kvm, the same debian installation that previously was failed (see previous tests), under emulator it works correctly in all cases. - when inkscape started on a physical machine, for each occurrence of the bug, this line appears in the journal: kernel: nouveau :04:00.0: bus: MMIO read of FAULT at 6013d4 [ IBUS ] - even when the bug does not occur, the first time I click to open the combo, the fonts update very slowly and the vertical scrollbar does not appear; after a few seconds the list no longer updates and I need to close the combobox and then reopen it for to see the vertical scroll bar appear and the list start updating slowly: from that moment, for all fonts (4083), it takes about 3 minutes to complete the loading of the entries. Now the error should be stabilized and reproducible. Good job! Antonio
Bug#960036: inkscape takes 100% CPU when opening font combobox
I did some other tests: on my system: - I removed all noto fonts + font cache reindex - test inkscape -> fonts preview ok - I edited ~/.config/gtk-3.0/settings.ini and changed line "gtk-font-name" with another existing font (for example Arundina) "gtk-font-name=Noto Sans 10" -> "gtk-font-name=Arundina Sans 10" - test inkscape -> problem - with "gtk-font-name=nonexistentfontname" - test inkscape -> fonts preview ok - with a different existing font "gtk-font-name=Dejavu Sans Mono 10" - test inkscape -> problem - I reinstalled all fonts noto - I commented line: "#gtk-font-name=Noto Sans 10" - test inkscape -> fonts preview ok on a fresh debian install (debian 10.4): - I installed desktop xfce4 and plasma/kde - I activated sid repository and installed inkscape + reboot - I am logged in to the xfce4 desktop - test inkscape -> fonts preview ok - I created file ~/.config/gtk-3.0/settings.ini with "gtk-font-name=Noto Sans 10" - test inkscape-> fonts preview ok - I am logged in to the plasma/kde desktop - test inkscape (file setting.ini is already present) -> problem - I removed font name "gtk-font-name=" - test inkscape -> ok - I inserted another existing font (for example Gentium) "gtk-font-name=Gentium 10" - test inkscape -> problem from the tests it would seem that the problem occurs from the combination: debian/sid + plasma/kde + config gtk-font-name (indicating any existing character) if can help... Antonio
Bug#960036: inkscape takes 100% CPU when opening font combobox
I have adopted this workaround: copy gtk-3.0 specific setting to inkscape config subdir: cp -a ~/.config/gtk-3.0 ~/.config/inkscape/ editing file ~/.config/inkscape/gtk-3.0/settings.ini comment line: ; gtk-font-name=Noto Sans 10 modify command start application in: XDG_CONFIG_HOME=/home/root/.config/inkscape inkscape Now inkscape works, without making changes to the system. However, I disabled the preview of the fonts because it takes too long. Antonio
Bug#960036: inkscape takes 100% CPU when opening font combobox
Quoting Antonio (2020-05-09 09:09:16) > >Noto fonts are known to provide many entries in font menus. > in fact I had to reinstall these fonts as they were used from the desktop With "these fonts" do you mean _all_ fonts-noto-* packages, or only (as I suggest) all except -extra? Did you experience _same_ delay initially, with and without the -extra fonts, or are you just still experiencing _some_ delay? > >Should be fine if avoiding only the *-extra packages (and the > >fonts-noto metapackage which recommends them) > This is true, but there is also a correlation with plasma/kde desktop > because to work with the noto fonts installed it was necessary: > > - remove fonts-noto-extra, fonts-noto-ui-extra, fonts-noto-cjk-extra > > - keep fonts-noto-color-emoji, fonts-noto-ui-core, fonts-noto-unhinted, > fonts-noto-core, fonts-noto-color-emoji, fonts-noto-mono, fonts-noto-cjk, > fonts-noto-hinted > > - modify the characters on plasma/kde, selecting a different fonts in the > "general" and "menu" items (for ex: dejavu sans): if on one of these items > there is "noto" the bug occurs again. > > or completely remove the known fonts and re-index the fonts, but in this > case the desktop changes its appearance... > so, for now, I have restored the for fonts Sorry, I don't understand you - you say "it is true" but then add a "but..." which (I assume) cancels that previous statement. So do you agree or do you disagree that you can reduce the burden of your system by avoiding fonts-noto-*-extra packages (and nothing else, i.e. no adjustments to desktop environment except if you have done something custom yourself to depend explicitly on one of the exotic flavors of Noto)? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
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 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 `- >
Bug#960036: inkscape takes 100% CPU when opening font combobox
>Noto fonts are known to provide many entries in font menus. in fact I had to reinstall these fonts as they were used from the desktop >Should be fine if avoiding only the *-extra packages (and the fonts-noto >metapackage which recommends them) This is true, but there is also a correlation with plasma/kde desktop because to work with the noto fonts installed it was necessary: - remove fonts-noto-extra, fonts-noto-ui-extra, fonts-noto-cjk-extra - keep fonts-noto-color-emoji, fonts-noto-ui-core, fonts-noto-unhinted, fonts-noto-core, fonts-noto-color-emoji, fonts-noto-mono, fonts-noto-cjk, fonts-noto-hinted - modify the characters on plasma/kde, selecting a different fonts in the "general" and "menu" items (for ex: dejavu sans): if on one of these items there is "noto" the bug occurs again. or completely remove the known fonts and re-index the fonts, but in this case the desktop changes its appearance... so, for now, I have restored the for fonts Il giorno ven 8 mag 2020 alle ore 21:53 Jonas Smedegaard ha scritto: > Quoting Mattia Rizzolo (2020-05-08 21:27:44) > > On Fri, May 08, 2020 at 09:25:13PM +0200, Antonio wrote: > > > After several tests I realized that the problem depends on these fonts: > > > "fonts-noto, fonts-noto-cjk, fonts-noto-cjk-extra, > fonts-noto-color-emoji, > > > fonts-noto-core, fonts-noto-extra, known-fonts-hinted, > known-fonts-mono, > > > known-fonts-ui-core, known-fonts-ui-extra, known-fonts-unhinted ". > > > Once removed, everything works fine. > > > > Ohh, this is very interesting. > > Could you please share this in the upstream bug I linked before, or > > would you prefer me to proxy the message? > > Seems it should say "noto-fonts-*" where it says "known-fonts-*" above. > > Noto fonts are known to provide many entries in font menus. > > Should be fine if avoiding only the *-extra packages (and the fonts-noto > metapackage which recommends them). > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#960036: inkscape takes 100% CPU when opening font combobox
Quoting Mattia Rizzolo (2020-05-08 21:27:44) > On Fri, May 08, 2020 at 09:25:13PM +0200, Antonio wrote: > > After several tests I realized that the problem depends on these fonts: > > "fonts-noto, fonts-noto-cjk, fonts-noto-cjk-extra, fonts-noto-color-emoji, > > fonts-noto-core, fonts-noto-extra, known-fonts-hinted, known-fonts-mono, > > known-fonts-ui-core, known-fonts-ui-extra, known-fonts-unhinted ". > > Once removed, everything works fine. > > Ohh, this is very interesting. > Could you please share this in the upstream bug I linked before, or > would you prefer me to proxy the message? Seems it should say "noto-fonts-*" where it says "known-fonts-*" above. Noto fonts are known to provide many entries in font menus. Should be fine if avoiding only the *-extra packages (and the fonts-noto metapackage which recommends them). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#960036: inkscape takes 100% CPU when opening font combobox
On Fri, May 08, 2020 at 09:25:13PM +0200, Antonio wrote: > After several tests I realized that the problem depends on these fonts: > "fonts-noto, fonts-noto-cjk, fonts-noto-cjk-extra, fonts-noto-color-emoji, > fonts-noto-core, fonts-noto-extra, known-fonts-hinted, known-fonts-mono, > known-fonts-ui-core, known-fonts-ui-extra, known-fonts-unhinted ". > Once removed, everything works fine. Ohh, this is very interesting. Could you please share this in the upstream bug I linked before, or would you prefer me to proxy the message? -- 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 `- signature.asc Description: PGP signature
Processed: Re: Bug#960036: inkscape takes 100% CPU when opening font combobox
Processing control commands: > tag -1 -moreinfo Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox Removed tag(s) moreinfo. > forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/841 Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox Set Bug forwarded-to-address to 'https://gitlab.com/inkscape/inkscape/-/issues/841'. > severity -1 normal Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox Severity set to 'normal' from 'important' -- 960036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960036: inkscape takes 100% CPU when opening font combobox
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 `- signature.asc Description: PGP signature
Bug#960036: inkscape takes 100% CPU when opening font combobox
On Fri, May 08, 2020 at 06:13:26PM +0200, Antonio wrote: > >Could you please give me more details? > > step for reproduce: > - start program > - open a blank document > - select tool "create and modify textual object" > - open combo for select the font (click on lateral arrow) Which, I believe, matches what I was trying. > -> a black vertical rectangle appears under the combo box and the desktop > freezes due to the high CPU effort I asked upstream, and they told me that it might happen if you have a lot of super complex fonts, as it generates previews on the first call to show the toolbar font list. Could you please provide us: fc-list | wc -l ? -- 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 `- signature.asc Description: PGP signature
Bug#960036: inkscape takes 100% CPU when opening font combobox
>Could you please give me more details? step for reproduce: - start program - open a blank document - select tool "create and modify textual object" - open combo for select the font (click on lateral arrow) -> a black vertical rectangle appears under the combo box and the desktop freezes due to the high CPU effort >What's the "previous version"? 1.0~rc1 or 0.92.4? previous version was 0.92.4-5 (debian/sid) >Also, since you managed to reproduce this with a plain upstream build, >did you also file this bug directly with them? I didn't send the bug to them, but I only reported this bug to Debian. Il giorno ven 8 mag 2020 alle ore 17:58 Mattia Rizzolo ha scritto: > Control: severity -1 important > Control: tag -1 moreinfo upstream > > Hi Antonio, thank you for the report. > > On Fri, May 08, 2020 at 04:10:32PM +0200, Antonio wrote: > > after updating inkscape to version 1.0, when I open the combobox to > select a > > font, the program consumes 100% of the cpu and the desktop freezes > > Could you please give me more details? Here I tried to: > * open a blank new file > * create a "text object" and typed in some random words > * selected the text > * tried to change the font using the menu that appears on the top left >side of the tool bar > and I'm not experiencing any issue. > > > Same thing if I recompile it from source (downloaded from their site). > > No effect if I remove configuration files. > > Note that previous version works well. > > What's the "previous version"? 1.0~rc1 or 0.92.4? > Also, since you managed to reproduce this with a plain upstream build, > did you also file this bug directly with them? > > -- > 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 `- >
Processed: Re: Bug#960036: inkscape takes 100% CPU when opening font combobox
Processing control commands: > severity -1 important Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox Severity set to 'important' from 'normal' > tag -1 moreinfo upstream Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox Added tag(s) moreinfo and upstream. -- 960036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960036: inkscape takes 100% CPU when opening font combobox
Control: severity -1 important Control: tag -1 moreinfo upstream Hi Antonio, thank you for the report. On Fri, May 08, 2020 at 04:10:32PM +0200, Antonio wrote: > after updating inkscape to version 1.0, when I open the combobox to select a > font, the program consumes 100% of the cpu and the desktop freezes Could you please give me more details? Here I tried to: * open a blank new file * create a "text object" and typed in some random words * selected the text * tried to change the font using the menu that appears on the top left side of the tool bar and I'm not experiencing any issue. > Same thing if I recompile it from source (downloaded from their site). > No effect if I remove configuration files. > Note that previous version works well. What's the "previous version"? 1.0~rc1 or 0.92.4? Also, since you managed to reproduce this with a plain upstream build, did you also file this bug directly with them? -- 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 `- signature.asc Description: PGP signature
