All installation and configuration problems and questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
by martinch » Fri Apr 14, 2023 3:34 pm
What Matt said. Google is on a mission to make Chrome energy efficient...and one of the easiest targets to save CPU cycles...is JavaScript timers on non-active pages. If the user can't see the page, why would we process any JavaScript on it? That's the thinking behind it me thinks.
Project Lead @ mDial -> https://github.com/TheBlode/mDial
-
martinch
-
- Posts: 273
- Joined: Thu Nov 15, 2018 9:14 am
- Location: England, UK
-
by taha12us » Sun Jun 04, 2023 9:24 pm
Disabling the below flag in Google Chrome did the job.
- Code: Select all
chrome://flags/#quick-intensive-throttling-after-loading
Version 114.0.5735.91 (Official Build) (64-bit)
Regards
-
taha12us
-
- Posts: 6
- Joined: Tue Aug 04, 2015 12:31 pm
by carpenox » Fri Jun 09, 2023 11:53 am
Alma Linux 9.4 | SVN Version: 3889 | DB Schema Version: 1721 | Asterisk 18.21.1 | PHP8
www.dialer.one -:- 1-833-DIALER-1 -:- https://linktr.ee/CyburDial -:- WA: +19549477572
GC: https://join.skype.com/ujkQ7i5lV78O | DC: https://discord.gg/DVktk6smbh
-
carpenox
-
- Posts: 2420
- Joined: Wed Apr 08, 2020 2:02 am
- Location: St Petersburg, FL
-
Return to Support
Who is online
Users browsing this forum: No registered users and 100 guests