[Bug]: Duplicated transaction requests

[hawkofsky]

Describe the bug

When I connect to arbiscan.io to interact with contract, any transaction request triggers multiple transaction requests in metamask.
It happens most of time.
So I checked the console of chrome browser and I found metamask conflicts with tronlink.
In the past, i didn't have such issue so it means the previous version of metamask didn't conflict with tronlink. but new version (11.14.1 updated at April 23, 2024) conflicts with tronlink, I think.
In the browser console (Inspect), it says tronlink provider initialized 6 times. and when i click contract function to interact with the contract, metamask shows 7 transaction requests of same function to be confirm.
I disabled tronlink extension and it was resolved.

Expected behavior

No response

Screenshots/Recordings

Steps to reproduce

1. Install tronlink chrome extension.
2. Install metamask chrome extension.
3. open link https://arbiscan.io/token/0xaf88d065e77c8cc2239327c5edb3a432268e5831#writeProxyContract
4. use any amount and address to call approve function

Error messages or log output

No response

Version

11.14.1

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

This is visible to all users who installed both of metamask and tronlink.
And it's so annoying.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.

[hjetpoluru]

Unable to reproduce the issue. hawkofsky could you please confirm if the issue exist.