Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slack Memory Leak? #1441

Open
bab5470 opened this issue Sep 16, 2023 · 3 comments
Open

Slack Memory Leak? #1441

bab5470 opened this issue Sep 16, 2023 · 3 comments

Comments

@bab5470
Copy link

bab5470 commented Sep 16, 2023

  • Wavebox Version:
    Wavebox: 10.117.10.2 stable
    Install Method: installer
    Wire Config: 1.2.17
    Chromium: 117.0.5938.62
    OS: win32/undefined

  • Operating System & Version:

  • Windows 11

Bug/Feature description

Wavebox slack tab using excessive amounts of memory after 1 day.

Steps to reproduce (if applicable)

Leave wavebox with slack open

ALT TEXT

@bab5470
Copy link
Author

bab5470 commented Sep 16, 2023

Killing that process and relaunching it memory usage drops significantly but then climbs over 24 hours until its back as high or higher.

@lens0021
Copy link

lens0021 commented Sep 17, 2023

I've upgraded a ram card of my laptop because it had troubles to run Wavebox and VS Code in the same time. I do upvote this if it helps.

@Thomas101
Copy link
Member

Hi, thanks for reporting. 1.5GB is high for Slack, my instance that's been running for a week is only at 250MB. There are couple of things worth trying...

  1. Clear the caches for slack by holding down the shift key and pressing the reload button in the top toolbar - this will clear any local caches in case you have a cache of some bad Slack code
  2. Disable any extensions under wavebox://extensions and see if the memory growth is the same - extensions that run within the tab, run within the same process so any memory leak with an extension could show up as problem with Slack

If neither of those work, can you reach out to [email protected], we can generate some diagnostics and see if there's anything else at play

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants