Dhoni returns as Chennai smash Titans

CLT20, RANCHI: Super Kings chase down a stiff total in their captain’s hometown.

AB De Villiers top-scored with 77, but it wasn't enough.

AB De Villiers top-scored with 77, but it wasn’t enough.

The Chennai Super Kings began their Champions League campaign with a near-perfect batting performance against the Titans from South Africa, who failed to defend an impressive score of 185-5.

After a lengthy break, MS Dhoni returned to action at his home town Ranchi’s JSCA International Stadium, much to the delight of his fans. He won the toss and bowled. AB de Villiers’s brilliant 77 should have been enough to ensure Titans a win today, but Chennai’s brute response led by Michael Hussey and Suresh Raina ended the contest very quickly.

Chennai lost Murali Vijay in the first over, thanks to a sharp arm-ball from Roelof van der Merwe. But Raina and Hussey added 89 runs in under eight overs to give the chase a powerful start.

When Raina came in, the floodlights at the venue failed for the second time in the day. According toRavichandran Ashwin, Raina’s been in bad form in the nets, but you wouldn’t have been able to tell that from the hitting that was to follow once the game resumed.

He waited on the backfoot for Morne Morkel to bounce him and the first ball he faced was pulled almost without any lack of control over midwicket for six. The over, the fourth of the innings, went for 24 runs with Hussey then carving Morkel a couple of times through the off-side.

The highlight of Raina’s innings, however, was the effortless waft off his pads for six off Marchant de Lange. When Raina fell to a loose drive to mid-off, Hussey kept up with the brutal hitting till he too got out on the same score of 47 to a mistimed loft down the ground.

Rowan Richards produced a three-wicket burst late in the game to make things a teensy bit interesting, but so far ahead were Chennai of the required rate, they coasted to the target with seven balls to spare.

Earlier in the day, the moment de Villiers came in to bat at the fall of Jacques Rudolph, the game became a one-man show. De Villiers is possibly the most versatile batsman of his time – he can play spin or pace, he can score on slow wickets or fast, and there’s no corner of the field he can’t hit a ball to.

He marked his arrival to the crease with a powerful straight drive off his South Africa colleague Albie Morkel. That shot didn’t go all the way for four, but signalled AB’s intentions. He proceeded to dismantle two of Chennai’s best. Ravindra Jadeja was put away for four sixes and Dwayne Bravo a couple.

At the other end was Henry Davids, who did a fine job making 52 in 43 but was put in the shade by de Villiers’ merciless assault on Chennai’s bowlers. Davids was stumped off a wide from Ashwin but the second-wicket partnership had produced 76 runs in six overs, setting up a large score for the Titans. But not large enough to keep the home team at bay.

How to Fix Google Chrome’s Shockwave Crashes?

If you regularly are seeing “Whoa! The Google Chrome has been crashed” message; then there likely is some problem in the system. Some occasional crash can occur, but regular crashes probably are caused by something that you can fix.

How to Fix Google Chrome’s Shockwave Crashes?

How to Fix Google Chrome’s Shockwave Crashes?

If your Google Chrome copy has taken on an inexplicable and sudden hatred for the Shockwave Flash, then here is a help for you. Read on as it is shown here that how to tame Google Chrome and make it to play nicely with Flash.

More than the other browsers, Chrome is susceptible particularly to a specific however common condition in which it merely will not coexist with Adobe Flash peacefully —frequent slowdowns as well as shockwave keeps crashing annoyingly as a common result. The tutorial below will help you obtain Chrome back to the quick self.

What Causes This Issue?

The reason that we’re talking about Google Chrome and not, Firefox is owing to the way Chrome deals with the Flash content. While the other browsers call on Flash installation of host system, Chrome consists of the internal Flash installation. If everything goes smoothly, it isn’t a problem—an internal Flash installation can be updated with each new release of Chrome.

Unfortunately, the things can pretty easily fall apart if Chrome gets puzzled and attempts to make use of both the internal Chrome’s installation of the Flash and the OS installation of the Flash. The consequence is temporary lockup, serious browser lag, and then browser-wide crash of the dynamic Flash instances. You do not realize what number of web sites make use of Flash until each single tab locks with crash warning—”Following plug-in is crashed: The Shockwave Flash”

How Will I Know that a Conflicting Installation of Flash Is Causing Crashes?

Firstly, despite the warning regarding Shockwave, the real warning has nothing actually to do with the Adobe Shockwave that is a separate multimedia system/program from Adobe Flash. Secondly, while not each instance of the Flash flaking in Chrome is attributed to Flash install conflict, now we’ve found it as the most popular reason why the users are experiencing this Flash-related issues.

How can you inform if a Flash clash is source of your difficulty and your shockwave keeps crashing? Run Chrome. In address bar, simply type about:plugins . After you press the enter key, you’ll be addressed with the complete list of all plug-ins installed inside Chrome (this is diverse from the user-installed Extension). Look down in the complete list of plug-in for Flash entry. If entry looks like the Flash (2 Files) there’s a very excellent chance the cause of the Flash-related crashes tends to be the conflict between these two.

In upper right corner of your browser window, there’s a small toggle which is labeled as [+] Details. Click that toggle in order to expand all the entries for the plug-ins. Then, return to entry for the Flash. You must see something like screenshot above: 2 entries for Flash, one is for the inner Chrome installation (which is highlighted in red) and one that is for the OS’s installation.

You require to click on Disable link for the Chrome’s internal Flash installation (take care that you halt the one that is located in Chrome AppData folder; however, not the detached stand-alone Flash’s installation).

Go ahead and then close tab and then shut your Google Chrome. Restart the Chrome and resume to normal browsing—stopover Adobe’s test page so as to make sure everything looks excellent. Remember, you’ll not be getting regular updates with every Chrome upgrade. Ensure to check for the updates at the download page of Adobe Flash and/or turn the update check on in your installation of this Adobe Flash.

Check Out For Conflicting Software

Any software on your system can conflict with Chrome because of which shockwave keeps crashing. This includes network-related and malware software which interferes with Chrome. Google Chrome also has one hidden page which can tell you if software on your computer is known to clash with Chrome. To access that, type chrome://conflicts in Chrome address bar and then press Enter.

You also can check software which crashes Chrome’s page on Google’s site for the list of software due to which shockwave keeps crashing. The page includes the instructions for solving the conflicts with a few conflicting software.

If you’ve conflicting software in your system, then you should update that to its latest version, uninstall it, or disable it. If you aren’t sure which software the module is related with, try to Google the name of that library.

Do a Malware Scan

Malware also can interfere with Chrome and make it to break down. If you are experiencing regular crashes, you must scan your system with antivirus software such as Microsoft security Essentials. In case, you have any antivirus software installed already, you may wish to get second opinion from other antivirus software.

Solve Flash Crash

It is found that Flash plugin Chrome can cause that to crash in a few cases. If your shockwave keeps crashing regularly, you may wish to try disabling internal Flash plugins and use the normal Flash plugin in Chrome.

Switch to New Profile

The Chrome crashes can be caused by any corrupted profile. You even can test this simply by creating new profile from the Chrome Settings screen. Open Settings page from the Chrome’s menu and then click Add a new user under the Users.

Change to new profile after making it and see whether the crashes continue to happen. You can log into Chrome with Google account so as to sync data from the old profile. But, Google recommends you to not copy any of the files from older profile folder by hands – they might be corrupted as well as causing the problems.

Other Fixes

For whatever reasons the disabling of built-in Flash’s doesn’t help, it is suggested to play around with diverse combinations. For example, try to turn off OS Flash installation rather than built-in Flash installation. Also, try visiting flash-based site in the Incognito Mode (whenever you enter this Incognito Mode, it will turn off all the Extensions which might or might not be causing the issues with Flash). Lastly, as last ditch efforts, you can also reinstall Chrome (if the Flash works in all other browsers but Chrome, this likely is the only option you’ve left).

You can make new profile for browser, or undergo a number of steps as well.

Source: http://savedelete.com/shockwave-keeps-crashing.html