Thy for the new version. Looks all quite good.
(05-18-2018, 11:00 PM)wOxxOm Wrote: [ -> ]See https://crbug.com/836230 - it's fixed in Chrome 67. As for Chrome 66, the only "solution" is to disable hardware acceleration in browser settings.
Thanks. I also get black squares on some websites.
In chrome://gpu creates a long error log.
Another trouble in Chromium 66 (Cent 3.4.3.39) - every 2 minutes a UDP request is sent to address 239.255.255.250 port 1900.
Chromecast? I have not found a way to disable. This is unacceptable!
I'm back on version 3.2.4.23.
(05-30-2018, 09:47 AM)NotWindbag Wrote: [ -> ]In chrome://gpu creates a long error log.
I dont know, how this work, but i have a google chrome 66 local installer. Chrome give more errors than Cent in chrome://gpu
[
attachment=586]
And gpu support features (in top of chrome://gpu) and perfomance (browserbench.org tests) are same.
By the way, Chrome 67 faster than 66 in browserbench tests.
Wait new version of CB
(05-30-2018, 09:47 AM)NotWindbag Wrote: [ -> ]Thanks. I also get black squares on some websites.
In chrome://gpu creates a long error log.
Another trouble in Chromium 66 (Cent 3.4.3.39) - every 2 minutes a UDP request is sent to address 239.255.255.250 port 1900.
Chromecast? I have not found a way to disable. This is unacceptable!
I'm back on version 3.2.4.23.
Yes, it should be Chromecast.
Check this link:
https://bugs.chromium.org/p/chromium/iss...?id=665572
(05-31-2018, 01:31 PM)Proton1983 Wrote: [ -> ]А если выпустить обновление до 67.0.3396.62 чтобы избавится от черных квадратов ? Я сейчас откатился до v3.2.4.23 там черных квадратов нет
We don't know.
This issue is specific to some video cards, we have not reproduced it yet.
Google Chrome stable channel has reached version 67. When will Cent Browser be updated? Current version is still stuck on Chrome 66.
(06-01-2018, 01:31 AM)DrVortex Wrote: [ -> ]When will Cent Browser be updated?
from
https://www.centbrowser.com/faq.html
3. How often do you release updates?
As a small team, we have no strict releasing cycle. But generally we follow these steps:
1. Release beta version, enter an observation period of 0-14 days, fixing bugs iteratively in this period.
2. Release stable version, enter an observation period of 0-7 days, may repackage the installer for minor bugs or release another update for severe bugs.
3. Trigger auto update if no more bugs are reported.
And chrome 67 released 3 days ago (
https://www.chromestatus.com/features/schedule)
(06-01-2018, 12:46 PM)Roderico Wrote: [ -> ]from https://www.centbrowser.com/faq.html
3. How often do you release updates?
As a small team, we have no strict releasing cycle. But generally we follow these steps:
1. Release beta version, enter an observation period of 0-14 days, fixing bugs iteratively in this period.
2. Release stable version, enter an observation period of 0-7 days, may repackage the installer for minor bugs or release another update for severe bugs.
3. Trigger auto update if no more bugs are reported.
And chrome 67 released 3 days ago (https://www.chromestatus.com/features/schedule)
?
I had read that.
This only mentions the schedule for Cent Browser - 7 day observation after release. It does not mention at what time after Chromium has updated does Cent Browser update.