I constantly get ipfs api accessible/inaccessible chrome notifications when i run something cpu and memory intensive on all cores.

[kotenok2000]

Describe the bug
A clear and concise description of what the bug is.
I get ipfs api accessible/inaccessible chrome notifications when i run something cpu and memory intensive on all cores.
To Reproduce
Steps to reproduce the behavior:

1. install ipfs desktop
2. Run boinc on all cores and run virtual machine with 4 gb ram allocated.
3. install ipfs companion and open lots of tabs.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Microsoft Windows [Version 10.0.22000.856]
• Browser: chrome
• Version: 104.0.5112.102

Additional context
Add any other context about the problem here.

[SgtPooki]

Thanks for submitting this issue @kotenok2000.

I believe this issue is with chrome or your computer specifically and not ipfs, but we may be able to investigate further if you can provide further information:

• Can you share your total memory allocation when these errors occur?
  • Do you have any extra memory?
  • Are other network operations or browser plugins working when in this state?

[kotenok2000]

No. I have 16 gb and 91% is used.
It happens when browser lags.

[github-actions]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[kotenok2000]

What more information do you need?

[SgtPooki]

@kotenok2000 Thanks for that information.

It seems like you're running out of resources for what you're trying to do. ipfs-companion has logic where it polls the running ipfs daemon every 3 seconds, to make sure the daemon is available. I imagine updating that logic to slow the polling time as requests are returning more slowly could help solve your and any others' similar issues.

However, for now, you can change that setting in ipfs-companion settings. See if that helps resolve your issue.

You could also start up the kubo daemon instead of IPFS Desktop too, to see if this helps your more resource intensive usecase.

I'll leave this issue open for making that polling logic smarter, but this is blocked until #666 is resolved.

[lidel]

It is unblocked (merged #1054).

@whizzzkid thoughts on solving the underlying annoyance and stopping online/offline notifications?

We could either:

• stop showing system notification when node state changes by removing notify calls from this function
• (if you feel it is useful at all) add a new toggle on Options page ⚙️, but it should be turned off by default.

My vote would be to simply remove these two notifications – user feedback has been consistent that they are annoying.

[whizzzkid]

@lidel I managed to miss this notification, I created a PR #1123 to kill these notifications. However there is already a toggle to turn on/off all extension notifications which seems to work. Maybe we can extend this to make this extension more granular.

It could inherit design from how @SgtPooki's work on tracking toggle's work out, but what I was thing was:

• Notifications <turn all on or off, we already have this>
  • Node State Change
  • Copy/Paste
  • News/Notification/Product Updates
  • etc.