Charlie Laabs

Looks like it's very similar on the back end. It's definitely doable, I just would need to find an elegant way to integrate it.

Similar to #180 Can you elaborate on your use case here? The only thing that's caused a memory leak is the process spawning a bunch of browser instances. A browser...

I thought I'd note, here are some commits I made to hopefully help resolve this: - https://github.com/claabs/epicgames-freegames-node/commit/6a08a53b6ab72b4db14821c001a322b6c005158c - https://github.com/claabs/epicgames-freegames-node/commit/287a706ae000cc49295dfba070377dd2710821a9

It looks like you're seeing the puppeteer hang issue (#164), and triggering the fix I put in to retry launching the browser (https://github.com/claabs/epicgames-freegames-node/issues/164#issuecomment-1002649474). It retries up to 30 times for...

Oh also, if you're seeing this regularly, you should probably set a memory limit on the container to prevent it from freezing your server. https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory `-m 2g` should be fine

I added the Chromium process pruning and lower amount of retries in https://github.com/claabs/epicgames-freegames-node/commit/1078cf8f3868bbe1f34c62997749ec45744c1a52 Hopefully that should handle it for now.

v4 of this project depends on Chromium and browser automation to login. Unfortunately, there are no modern Chromium or Chrome versions available on Alpine or Debian Linux for armv6/v7. It...

I can't know for sure, but it's likely your volume just isn't mounted correctly, so the config file isn't being picked up and it's generating the default one. You can...

No you shouldn't expect anything for 2 reasons: 1. When idling (between scheduled free game checks), the container completely exits the Node process to save on memory (About 100MB saved)....

I'll add in that I'm also seeing this issue with SDL2 applications. It essentially nullifies the ability to use some buttons on the N64 side of the adapter, since the...