Linux: 100% CPU usage Kernel 5.4+

Support
1

Version 1.0.197

OS: Manjaro linux 19 xfce

Since last week, whenever I open the app, CPU goes to 100% and system becomes slow. I have to wait for about 10 minutes and close other programs to get it to normal. The problem is ocurring both for the appimage and also webstore app.

2

Could you check the log and console? https://joplinapp.org/debugging

3

Also, when exactly is it freezing? If you’re able to install the linux-lts kernel, does the issue go away?

sudo pacman -S linux-lts should be all that’s needed. Then, reboot and try Joplin again.

4

I’m getting these warnings, but I dont know what they mean:

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • If you’re updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
  • Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Connect(HeaderComponent), Connect(MainScreenComponent), Connect(NavigatorComponent), Connect(NoteListComponent), Connect(NoteTextComponent), Connect(RootComponent), Connect(SideBarComponent), Provider
printWarning @ /tmp/.mount_JoplinK7wbRR/resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:11494
/tmp/.mount_JoplinK7wbRR/resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Connect(HeaderComponent), Connect(MainScreenComponent), Connect(NavigatorComponent), Connect(NoteListComponent), Connect(NoteTextComponent), Connect(RootComponent), Connect(SideBarComponent)

5

I have tried changing kernels, but the issue remains. Curiously, starting joplin makes firefox use a lot of CPU especially when youtube is running. If I close the youtube tab, CPU becomes normal in about 30-40 sec.

6

So, 5.4 is still having the issue? I’m asking because kernel 5.5 and 5.6 both are problematic due to a single change breaking multiple frameworks and apps

7

Actually I was on 5.4 kernel itself when the issue appeared first. I tried 5.5 and 4.19 kernels but did not help.

1 Like
8

Thanks for verifying that.

The log information you linked above wasn’t useful. Those are normal warnings.

Could you share your ~/.config/joplin-desktop/log.txt here? That would help others solve your issue

9

log.txt (364.6 KB)

1 Like
10

If you could just upload it, that’d be easier. There’s a character limit per post and it may have cut off

11

I’m sorry. Will upload.

1 Like
12

Thanks. If you can add it to the original post, it will have less chance of getting lost. I’m not sure how to help you further, but the community here are crazy good at these things

13

Thanks for the prompt help. Appreciate it.

1 Like
14

You’re quite welcome. Welcome to the forums and enjoy perusing all of it at your leisure. :wink:

15

I found the issue. Its firefox. With google chrome app is running smoothly without spiking RAM.

16

If you want to keep using firefox, this fix worked for me https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu-usage-for-30-seconds-when-launching-chromium

17

Thanks!! I did not think that the issue could have been due to fonts. I realised that I had installed Google-fonts package and had huge amount of fonts, which was precisely the problem. Removed it and now everything is back to normal.

1 Like