You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After restarting/turning on the computer and booting into XP, trying to run the browser shows a window, then closes immediately after. Opening the browser afterward works fine, it only crashes once on a fresh boot.
To Reproduce
Steps to reproduce the behavior:
Double click Supermium on the desktop after a restart of the computer, and after loading, it crashes.
Expected behavior
The browser should start the first time, rather than having to re-open it for it to load correctly.
Desktop (please complete the following information):
OS: [e.g. Windows XP SP2 x64]
Bitness of browser: x64
Additional context
This only seems to happen on XP, Vista and higher don't have this issue. I've had this issue across several versions of Supermium, it doesn't seem to be caused by any one version.
The text was updated successfully, but these errors were encountered:
I believe it's related to issue #1030 (and possibly #755 and #964).
In this case the problem seems to be a out of memory error when trying to decode a bitmap, which kills the renderer. Some synchronization primitive changes are also pending which may also have an impact on this issue.
Describe the bug
After restarting/turning on the computer and booting into XP, trying to run the browser shows a window, then closes immediately after. Opening the browser afterward works fine, it only crashes once on a fresh boot.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The browser should start the first time, rather than having to re-open it for it to load correctly.
Desktop (please complete the following information):
Additional context
This only seems to happen on XP, Vista and higher don't have this issue. I've had this issue across several versions of Supermium, it doesn't seem to be caused by any one version.
The text was updated successfully, but these errors were encountered: