Hello, I'm experiencing an issue with Kameleo’s high proxy traffic usage. I ran a test to compare it with AdsPower: 10 Chrome browsers v139 on Win10/11. Kameleo was using just empty tabs, while AdsPower was using its default start page.
Data usage:
— Idle: 135 KB
— 10 AdsPower running: 6.02 MB
— 10 Kameleo running: 250 MB and increasing
How is that possible?
Previously, Kameleo’s traffic usage in real tasks compared to AdsPower was about 2 times higher, but starting August 21, it became 4 times higher.
Hi, I forgot to notify you here that we were able to fix this by disabling optimization hints loading in Chroma by default. See details here: https://kameleo.io/browser-kernel-releases
We enabled the bandwidth saving option on Chroma 139 as well. We released the updated Chroma 139 kernel today. It will auto-download if you start a Chrome 139 profile. More information here: https://kameleo.io/browser-kernel-releases
Thanks for the update. I'm facing a strange Kameleo behavior, testing Chrome 140 on two separate VPSs, on the 1st VPS Kameleo Chrome 140 is using extra data, but on the 2nd VPS everything is ok. And I know that the 1st VPS was ok on Sep 16, the 2nd VPS was ok yesterday and is ok today. Reinstalling Kameleo on the 1st VPS and removing folders didn't help. Also all kernels was removed from both VPSs but still the same result.
My name is Jovan, and I'm a Technical Support Agent for Kameleo. We really appreciate this additional input that you've made. I've went ahead and created a ticket about this subject, the ticket ID is 11858.
In the ticket we've asked for some additional information if you don't mind sending it to us. Thank you again. :)
Chroma 139 will also be updated during this week, to eliminate the issue on all Chroma versions. In the meantime please use Chroma 140 or versions before Chroma 139.
Hello, thank you for the report. We will start examination asap and fix it. Most likely it is some data that Chroma is fetching to optimize working (like dictionaries). We will find it and disable it by default.
In your report you mention "idle: 135 KB". What do you mean exactly?
Hello, I'm experiencing an issue with Kameleo’s high proxy traffic usage. I ran a test to compare it with AdsPower: 10 Chrome browsers v139 on Win10/11. Kameleo was using just empty tabs, while AdsPower was using its default start page.
Data usage:
— Idle: 135 KB
— 10 AdsPower running: 6.02 MB
— 10 Kameleo running: 250 MB and increasing
How is that possible?
Previously, Kameleo’s traffic usage in real tasks compared to AdsPower was about 2 times higher, but starting August 21, it became 4 times higher.
Hi, I forgot to notify you here that we were able to fix this by disabling optimization hints loading in Chroma by default. See details here: https://kameleo.io/browser-kernel-releases
Hi, thanks! I can confirm that 140 is good now, 139 is still using extra data.
We enabled the bandwidth saving option on Chroma 139 as well. We released the updated Chroma 139 kernel today. It will auto-download if you start a Chrome 139 profile. More information here: https://kameleo.io/browser-kernel-releases
Thanks for the update. I'm facing a strange Kameleo behavior, testing Chrome 140 on two separate VPSs, on the 1st VPS Kameleo Chrome 140 is using extra data, but on the 2nd VPS everything is ok. And I know that the 1st VPS was ok on Sep 16, the 2nd VPS was ok yesterday and is ok today. Reinstalling Kameleo on the 1st VPS and removing folders didn't help. Also all kernels was removed from both VPSs but still the same result.
Hello,
My name is Jovan, and I'm a Technical Support Agent for Kameleo. We really appreciate this additional input that you've made. I've went ahead and created a ticket about this subject, the ticket ID is 11858.
In the ticket we've asked for some additional information if you don't mind sending it to us. Thank you again. :)
Chroma 139 will also be updated during this week, to eliminate the issue on all Chroma versions. In the meantime please use Chroma 140 or versions before Chroma 139.
Hello, thank you for the report. We will start examination asap and fix it. Most likely it is some data that Chroma is fetching to optimize working (like dictionaries). We will find it and disable it by default.
In your report you mention "idle: 135 KB". What do you mean exactly?