Testing OpenCV TrackerMIL 'Tracking error' on high resolution

Import Userrequested to merge
ov/issue_8894_opencv into develop

This contributes a regression test reproducing a bug from #8894 (closed)

Motivation and context

A 'Tracking error' message notification popping up when tracking shapes with OpenCV's TrackerMIL. Its cause was shown to be memory issues when using an OpenCV tracker on frames with high resolution (ca. 5000x5000)

How has this been tested?

  • Generate 3 pics 5000x5000 each containing an object to be tracked
  • Open task job and load OpenCV library
  • Go to the 2nd frame
  • Create a shape with TrackerMIL, assert that UI state is correct
  • Go to next frame
  • Assert that no 'Tracking error' notification message popsup

The test is marked as skipped for now since the fix is still to be implemented.

WARN: Cypress crashes if this test is enabled (this is expected for now)

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary (cvat-canvas, cvat-core, cvat-data and cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Merge request reports