ZxingScannerComponent is not releasing all resources - BrowserCodeReader still trying to decode after ngDestroy

[RafalOddslife]

Describe the bug
BrowserCodeReader is trying to decode even after destroying ZxingScannerComponent
Affected version: "@zxing/ngx-scanner": "^17.0.1"

Code

<button (click)="scannerVisible = !scannerVisible">Toggle scanner</button>
<zxing-scanner *ngIf="scannerVisible"></zxing-scanner>

To Reproduce
Steps to reproduce the behavior:

1. Go to simple repro in stackblitz
2. Use toggle button to init and destroy zxing-scanner component (the more you do this, the bigger the leakage)
3. Open chrome devtools, open Performance tab and capture new recording
4. BrowserCodeReader is still trying to decode even after destroying component

Expected behavior
All resources released

Screenshots

[werthdavid]

Thanks! Created a PR, feel free to take a look, my tests were fine. I'll merge it tmrw if nobody filed an objection..

[RafalOddslife]

I've just checked and I'm unable to reproduce the error for my repro so it appears to be working correctly. Appreciate fast reaction!

[werthdavid]

Released in 17.0.2