[Bug] Memory leak detected (Occurs on .rpm, and .appimage)

[pinbuck]

Discord Account

evilwizard1041

Operating System

Fedora 41

Linux Only ~ Desktop Environment

KDE on Wayland

Package Type

rpm

What happens when the bug or crash occurs?

The client seems like average, negligibly different. Tested with and without plugins, I still get the memleak.

On linux, I have generic issues with screenshare crashing the client and xwayland, otherwise everything's considered normal.

I haven't (noticed) higher than average memory consumption.

What is the expected behaviour?

I expect equibop to launch and give no significant errors, when vesktop launches it gives no issues.

How do you recreate this bug or crash?

1. Launch equibop in the terminal, with or without --trace-warnings

Debug Logs

equibop --trace-warnings
Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: rpm
Checking for update
(node:4770) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 did-stop-loading listeners added to [WebContents]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at _addListener (node:events:593:17)
    at WebContents.addListener (node:events:611:10)
    at WebContents.once (node:events:655:8)
    at node:electron/js2c/browser_init:2:76434
    at new Promise (<anonymous>)
    at waitTillCanExecuteJavaScript (node:electron/js2c/browser_init:2:76421)
    at _.executeJavaScript (node:electron/js2c/browser_init:2:76638)
    at Re (VCDMain:19:96)
Update for version 2.1.1 is not available (latest version: 2.1.1, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is null
[4806:0203/182129.608220:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

Request Agreement

• I have searched the existing issues and found no similar issue
• I am using the latest Equibop and Equicord versions
• This issue occurs on an official release (not just the AUR or Nix unofficial packages)

[refurbishing]

you can safely ignore that "memory leak" console log, and about the screenshare stuff see #47