IonChange event triggers on wrong component due to caching

I have multiple Vue component which are all different pages of my app. Each page has a ion-searchbar component in it. Each ion-searchbar has a @ionChange event that filters a list on the page.

The strange thing is now, that when I type something in a searchbar in page A, the ionChange event of page B triggers. I think it is due to Ionic or Vue caching the ion-searchbar component as I find this in the stack trace: Object.onIonChange._cache.<computed>._cache.<computed>

That trace is executed once for the current page and another time for the wrong page. Is there a fix to turn off this caching or what could be the issue here?

code? or even better a project demonstrating the issue?