Chrome, Google’s web browser is said to have problems in incognito mode in its Android version and some of user’s online behavior is stored in history as a consequence.

Google’s Chrome web browser,right from its debut has faced criticism because it uses the WebKit Engine which uses lot of RAM and slows down the machine. Now a bug has been reported in Chrome browser in Android version in its  Incognito mode. The Incognito mode was introduced in 2012 by Google for its Chrome browser, a feature now present in all of its variants, on Android, iOS, Mac, Linux, and Windows.

You can crash the latest version of Google Chrome with a simple tiny URL. Just rolling your mouse over it in a page, launching it from another app such as an email client, or pasting it into the address bar, will kill either that tab or the whole browser.

It's perfect for pranking friends by sending it to them in emails and messages. What's cool about this bug is that it triggers a fatal exception rather than the usual memory access violation error caused by an overrun buffer, heap corruption, or similar – even in released code. This means some part of the executable was reached that the programmers never expected normal users to hit.

From almost 250 security flaws reported for the top 20 software solutions with the most number of vulnerabilities discovered in the first month of the year, Google Chrome came at the head of the list, according to a security service company.

Google is dedicated to increasing the safety of all its products to such an extent that sometimes cybercriminals focus their efforts on exploiting flaws on other platforms. The large amount of flaws recorded for the web browser can be explained by the fact that third-parties are incentivized by the company’s Security Reward Programs to find new ways to bypass protections implemented in Chrome.

The Chrome browser is generally considered the most secure Web browser, and it also tends to do the best in hacking competitions. This is in part thanks to the solid security architecture of Chrome, and to its security engineers, who keep adopting strong security designs and policies.

There's always a compromise between security and flexibility/freedom to do something. Security is very much about reducing the attack vectors, which generally means reducing the freedom to use some features. Some of those security decisions can go too far sometimes, such as the decision to only allow Chrome extensions to be installed from the Chrome store, when there could have been alternative solutions that are not as restrictive.