This bug ( crbug.com/849080 ) should have been fixed in 68.0.3440.25. Could you please confirm that you are using a version prior to this? The bug report says you are using 67.0.3396.99.

Currently, I m using chrome Version 68.0.3440.84. Still, this issue is occurring.
Please find the latest attachment.

Deleted: nonscalingissueInPattern.html 945 bytes

nonscalingissueInPattern.html 945 bytes View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

pdr@, could you take a look at this. First step is to verify the problem.

Yeah this is a problem. I've attached a minimized testcase.

In Pre-SPv175 we forced a subtree paint invalidation on non-composited transform changes. SPv175 no longer does that, so we need to explicitly update objects with non-scaling stroke when an ancestor transform changes. We fixed this for <rect>s/<path>s/etc under a changing transform in  https://crbug.com/849080 . This bug is about non-scaling stroke under <pattern> which is under a changing transform.

Deleted: nonscalestroke.html 715 bytes

nonscalestroke.html 715 bytes View Download

The NextAction date has arrived: 2018-08-13

Any update on this? Can we expect this issue fix in upcoming chrome release?

Unfortunately this will not be fixed in the next release.

As a workaround, you can change a property on the pattern to force chrome to notice the change. For example:
pattern.setAttribute('patternUnits', pattern.getAttribute('patternUnits'));

In your example this would be:
var interval = setInterval(function(){
  ...
  scalableEle.attr("transform", "scale("+increaseScale+")");
  patternZoomTest.setAttribute('patternUnits', patternZoomTest.getAttribute('patternUnits'));
  ...
}