Other browsers (firefox, safari, edge, opera) continue to work correctly and also chrome version 63 works good. 

Just something from chrome version 64 is broken. Please let us know if we can provide any specific details. We tried to narrow down the cause but had no success so far.

Any chances you have something listed in chrome://crashes? Chrome can synthesize crash reports if it notices itself freezing, so maybe it did that in time to give some insight as to what went wrong. 

I dont have a crash reports on mac machine. I had to force power it down. But I do have crash report on my Win7 machine. It suffered from same problem.

Local Crash ID 9e1b060e-a6b0-495d-9c99-7f3c214e7090
Crash report captured on Tuesday, February 13, 2018 at 5:53:40 PM. It's uploaded.

On otherhand there was patch yesterday night I believe and it fixed my problem.

Version 64.0.3282.140 (Official Build) (64-bit) - performance issue
Version 64.0.3282.167 (Official Build) (64-bit) - new build, no perf issue. works awesome

Thank you
Rahul

Glad that the update seems to help.

Could you peek at that crashes page again in a bit and see if it replaced the 
local crash ID with a shorter one that doesn't say it's local?

Yes, It did.

Uploaded Crash Report ID bc64ba7369eb861e (Local Crash ID: 9e1b060e-a6b0-495d-9c99-7f3c214e7090)
Crash report captured on Tuesday, February 13, 2018 at 5:53:40 PM, uploaded on Wednesday, February 14, 2018 at 5:29:12 PM

So that report corresponds to some sort of lockup in the graphics process, which then gets restarted to recover from it... seems improbable that it would also affect your Mac. 

I think I'll leave it to other triage folks to try to follow your instructions..

Thank you.

Please do let me know if you need any other information.

tibdewal.rahulkumar@ Thanks for the issue.

Tested this issue on Mac OS 10.13.1 on the reported version 64.0.3282.140,latest Canary 66.0.3348.0 and unable to reproduce the issue the following the steps given in the original comment.
Could not observe any hang on the machine after installing a remo on Mac OS.

As Crash ID is given in comment #6, requesting someone from Inhouse team to please look into this issue and help in further triaging.

Thanks..

Stack trace and Magic signature of the above Crash i'd looks similar to issue 597700. Hence merging into it. Please feel free to un merge if not the case.

Thanks!!