Hi,

I'm seeing an incredibly large number of BUFFER OVERFLOW events when monitoring my system with SysInternals ProcessMonitor, which appear to be related to the Qpixmap.load call (passing in a string to the PNG file)

The code section where this occurs is as shown below

My understanding was that sometimes when calling a Win32 API if you don't know the size of the buffer, you would pass in a NULL pointer, and that may result in a BUFFER OVERFLOW, however following this you would also get a result that told you the correct size for the buffer, so you could obtain the right buffer size and try again.

This looks like it's trying much too hard.