At present, the second time that content is loaded with the core on dynamic platforms, undefined behaviour can occur due to the fact that the interframe blending arrays are not correctly initialised. This is a previously hidden bug (which should never occur on dynamic platforms...), and it seems to be platform-dependent: the core has always functioned correctly in the past, and it still functions correctly on half my devices. It is likely that an OS (glibc) update has revealed the underlying issue...
This PR simply ensures that the interframe blending configuration is properly reset inside retro_deinit(). This 'forces' correct initialisation each time the core is loaded.
At present, the second time that content is loaded with the core on dynamic platforms, undefined behaviour can occur due to the fact that the interframe blending arrays are not correctly initialised. This is a previously hidden bug (which should never occur on dynamic platforms...), and it seems to be platform-dependent: the core has always functioned correctly in the past, and it still functions correctly on half my devices. It is likely that an OS (glibc) update has revealed the underlying issue...
This PR simply ensures that the interframe blending configuration is properly reset inside
retro_deinit(). This 'forces' correct initialisation each time the core is loaded.