[@azure/communication-calling] MaxListenersExceededWarning after 11 calls

[samueleiben]

• Package Names and versions: @azure/communication-calling (1.25.1), @azure/communication-common (2.3.1)
• Related documentation: https://learn.microsoft.com/en-us/azure/communication-services/how-tos/calling-sdk/manage-calls?pivots=platform-web

Describe the bug After starting 11 calls, the console shows the following warning:

MicrosoftTeamsAddOn.ts:242 MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 statusChanged listeners added. Use emitter.setMaxListeners() to increase limit
    at _addListener
    at EventEmitter.addListener
    at AudioEffectsStatusManager.on
    at AudioEffectsFeatureImpl.updateAudioEffectsStatusManager
    at AudioEffectsFeatureImpl.initialize
    at ExtensibleFeatureImpl.getApiObjectInstance
    at LocalAudioStream.feature
    at v.value
    at TeamsCallImpl._handleAudioEffectsOperations
    at TeamsCallImpl.startCallInternal

To Reproduce Steps to reproduce the behavior:

1. Repeat the following two steps 11 times:
2. Start a call using callAgent.startCall
3. Accept the call and end it again.

Expected behavior No warning is shown in the console.

Additional information I am using two Microsoft Teams participants for the calls (instead of a Microsoft Teams participant and a phone number).

[github-actions[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

[samueleiben]

This seems to have been fixed in 1.26.1