Strange Subscriber Memory Leak when using mat-radio-group

[dottodot]

I'm not sure why this is happening and can't see an obvious reason but when I use mat-radio-group in my template I seem to get and big Subscriber memory leak, and if I remove mat-radio-group that leak no longer occurs.

  <mat-radio-group [formControl]="shopService.sort" aria-label="Select an option">
    <mat-radio-button [value]="option.query" *ngFor="let option of shopService.sortOptions">{{option.title}}
    </mat-radio-button>
  </mat-radio-group>

if I remove the mat-radio-group so I just have the mat-radio-button I also don't get the leak. i.e

   <mat-radio-button [value]="option.query" *ngFor="let option of shopService.sortOptions">{{option.title}}
    </mat-radio-button>

Just a bit confused as to why this would be happening.

[crisbeto]

At what point are you taking the memory snapshot? I tried a similar setup to the one you posted, but I never got any references to a Subscriber.

[dottodot]

@crisbeto So I'm taking a snapshot on my home page then navigating to the page that uses mat-radio-group and repeating several times and then taking another snapshot. I have also tried on a clean install and can't replicate. So don't understand how this can be happening, all I know is I don't get the leak when mat-radio-group isn't present.

[crisbeto]

That's odd. Have you tried shaving off as much as possible? E.g. removing the ngFor and the formControl?

[dottodot]

@crisbeto OK so if I remove the formControl I don't get the issue.

[dottodot]

the only thing I can think of is the formControl is linked to the following in a service

  sort = new FormControl('popular');

then elsewhere I'm using this.shopService.sort.valueChanges which is part of observable chain. This however is subscribed to using the async pipe which I've always assumed handles the unsubscribing for you.

[dottodot]

So I changed the mat-radio-group to use [(ngModel)] rather than [formControl] and the problem has gone.

[crisbeto]

Looks like this was resolved and the original issue was coming from the Angular forms module.

[angular-automatic-lock-bot]

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.}