Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

MatSideNav autosize runs into ngZone 100% CPU

See original GitHub issue

Bug, feature request, or proposal:

Bug: regression MatSideNav autosize runs into ngZone

What is the expected behavior?

autosize code should run outside ngZone

What is the current behavior?

autosize code runs inside ngZone

What are the steps to reproduce?

<mat-sidenav-container autosize>
  <mat-sidenav [opened]="isSidenavOpened" [mode]="'side'"></mat-sidenav>
</mat-sidenav-container>

https://stackblitz.com/edit/angular-material2-issue-fn9sts?file=app/app.component.html

What is the use-case or motivation for changing an existing behavior?

It pushes CPUs to their limit, 100% constant usage.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular CLI: 6.0.0 Node: 8.9.4 OS: win32 x64 Angular: 6.0.0 Material: 6.0.1

Is there anything else we should know?

Does not happen unless this code is present [opened]="isSidenavOpened" [mode]="'side'"

Issue Analytics

State:
Created 5 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

crisbetocommented, Jul 4, 2018

I can’t say since it depends on when the caretaker gets to merging the PR. The issue got introduced in 6.3.2 so you should be able to stick with 6.3.1 until the fix gets in.

0reactions

angular-automatic-lock-bot[bot]commented, Sep 9, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}