Firstly, you need to uncheck "Other settings"->"Enable auto update of Cent Browser" to prevent further auto update.

For installed version, you can uninstall the newer version(keep profile untouched) or remove registry item(HKEY_CURRENT_USER\SOFTWARE\CentBrowser), then install the older version.

For portable version, you can extract the newer version to the portable directory and overwrite all files, or delete chrome.exe and rename old_chrome.exe to chrome.exe.

If you get "Profile corrupted" warning on startup, you need to manually delete "Web Data" and "Web Data-journal" under "User Data\Default" and restart the browser.

If you get logged out every time after closing the browser, you may need to manually delete "Cookies" and "Cookies-journal" under "User Data\Default" and restart the browser.

You can see the location of "User Data" by opening chrome://version/ in the browser, it is included in "Profile Path".

As a small team, we have no fixed release 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.

This browser checks update every 6 hours automatically after startup. If you don't want it, you can uncheck "Other settings"->"Enable auto update of Cent Browser" to disable auto update. There is also an "Check for update" command in the main menu(three dot). In rare cases the browser will be updated once if the new installer was downloaded complete and started to run before you unchecked that option.

You can press ALT to close menus and ESC to close popup dialogs.

"[NOT RECOMMENDED]" means there may be side effect of changing this option. For example, changing "Disable HTML5 canvas fingerprinting" may lead some scripts to crash, and changing "Run Flash player in sandbox" may increase the risk of Flash vulnerabilities.

Unless your RAM is very tight, we don't recommend you to check them. But no performance regression is observed about those options till today.

We don't recommend you to do that. If you insist, you can change "Under the hood"->"Privacy"->"Content settings..."->"Flash" to "Block sites from running Flash" and chrome://flags/#run-all-flash-in-allow-mode to "Default".

Probably fault of hardware acceleration, you can recover by killing GPU process. One of the approaches could be executing the following command in cmd.exe:
wmic process Where "Name='chrome.exe' AND CommandLine Like '%type=gpu-process%'" Call Terminate

We tend to add or strengthen functional and useful features(especially when there are no good extensions). We will try our best to prevent this browser from getting bloated, but we are not chasing for extremely simple. Our final decision would make balance among performance, features and maintenance.