QBackingStore::endPaint() called with active painter; did you forget to destroy it or call QPainter::end() on it?

[QuentinMcCarthy]

The problem:

Just today while adding new mods to my modlist, mo2's log has started getting spammed with the error in title:
[2024-04-16 06:21:31.386 W] QBackingStore::endPaint() called with active painter; did you forget to destroy it or call QPainter::end() on it?

It's never-ending, with the time actively counting upwards as I'm typing this on the latest entry. The only way I've found to get it to stop is to close mo2 and reopen it.

To Reproduce:

I'm unsure the exact cause, but all I've been doing is installing mods, deleting downloads, enabling/disabling mods, etc etc. This issue only started happening today and the only thing I've done differently from normal is add notes to a couple mods as they're off-site (non-nexus).

Environment:

• Mod Organizer Version that exhibits the issue: Latest, 2.5.0
• Last Mod Organizer Version that did not exhibit the issue (if applicable):
• Desktop OS/version used to run Mod Organizer: Windows 11 Home Build 22631.3296 (update TBD)

Details:

MO2 has been particularly unstable today for some reason, which may be related to my PC. The downloads gets refreshed randomly stating an error that I can't remember, and it at one point stopped recognising Nemesis Behaviour Engine, stating "mod/" was not recognised or some such.

Link to Mod Organizer logs:

I'm unable to reliably reproduce the issue due to not accurately knowing the cause. If it happens again today I will edit this post and add the logs.

USVFS:

Create a GIST which is a paste of your latest USVFS log, and link them here.
Do NOT paste your full USVFS logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the USVFS logs!

MO Interface:

Create a GIST which is a paste of your mo_interface logs, and link them here.
Do NOT paste your full mo_interface logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the mo_interface logs!