Marker Tracker Causes Droped Frames When Calling Start

Hello everyone,
I have some problems related to marker tracking after upgrading the Magic Leap 2 operating system to the latest version.
Using the QR scanner with OS version 1.3.0 everything was fine. When I upgraded the OS to version 1.6.0 which was offered on the hub, the marker tracker showed an unexpected behavior: when I start the scanner the whole system freezes for a few seconds and then continues to work properly. The problem is that I am developing an application based on QR code recognition and this freezing of the application makes it unusable. Does anyone have any suggestions regarding reading QR codes with the new update? I'm sure it's a problem related to the new software version because using the same application on a device that hasn't been updated yet, the problem doesn't come out. Thanks in advance

Unity Editor version: 2022.2.21
ML2 OS version: 1.6.0
Unity SDK version: from 1.3.0 to 1.6.0
Host OS: (Windows/MacOS) windows

Do you mind verifying the Unity SDK Version that you are using in the project? Is it correct for me to assume that you are not using the OpenXR APIs?

See Unity SDK Versions:

I made a mistake sorry.
I'm using
Unity SDK version: 1.12.1
MLSDK: 1.5.0

For trancking QR codes I user MarkerTrackingExample that uses MLMarkerTracker methods

Thank you for that information. Unfortunately, starting the marker tracker does impact the application's performance. That said, performance of starting the marker tracker tracker will be improved in the OpenXR version of Marker Understanding in the 2.2.0 Unity SDK.