FlareSolverr / FlareSolverr

Proxy server to bypass Cloudflare protection

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Chrome.exe (v124) processes keep running on background

andtoliom opened this issue · comments

Have you checked our README?

  • I have checked the README

Have you followed our Troubleshooting?

  • I have followed your Troubleshooting

Is there already an issue for your problem?

  • I have checked older issues, open and closed

Have you checked the discussions?

  • I have read the Discussions

Environment

- FlareSolverr version: 3.3.17
- Last working FlareSolverr version: 3.3.16
- Operating system: Windows 11
- Are you using Docker: [yes/no] no
- FlareSolverr User-Agent (see log traces or / endpoint): Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
- Are you using a VPN: [yes/no] no
- Are you using a Proxy: [yes/no] no
- Are you using Captcha Solver: [yes/no] no
- If using captcha solver, which one:
- URL to test this issue: any

Description

Chrome processes remain active in the background and are never closed, they accumulate until the computer crashes. Flaresolverr is not terminating the processes once it solves the CF challenges. This is happening since the new version of chrome v124. Before it worked perfectly.

Logged Error Messages

No logs messages.

Screenshots

c52b2235cf0692b6b0b16aeea7857abe

If you use the v3.3.17 precompiled binaries (with v123 Chromium), does the issue not occur?

Yes works, but I need to use Chrome v124

Why specifically v124?

Why specifically v124?

I use some chrome extensions and I have to edit the source code to load a custom chrome profile

Yea, this seems to be specific to Chrome v124, as it affects v3.3.16 too.

You can uninstall Chrome v124 and install v123 instead in the mean time - https://filecr.com/windows/google-chrome/?id=544228864100

Yea, this seems to be specific to Chrome v124, as it affects v3.3.16 too.

You can uninstall Chrome v124 and install v123 instead in the mean time - https://filecr.com/windows/google-chrome/?id=544228864100

Thank you! I will work with v123 till there is a solution for new Chrome versions

Alternatively, build your own binaries, which will use Chromium v123:

python src/build_package.py

Then you can reinstall Chrome normally, so you're not stuck on v123.