Supermium 124.0.6367.245 semi-crash

[tmcdos]

Describe the bug When I start Supermium 124.0.6367.245 - it opens the blank page but Win7 SP1 shows a popup error about invalid instruction.

To Reproduce Steps to reproduce the behavior:

1. Use the following CMD file to start Supermium

   start /d "D:\PROGRAM\Inet\Chrome\124.0.6367.245" /b chrome.exe --classic-omnibox --classic-omnibox-border --enable-features=SupermiumCustomTabs --disable-features=TabHoverCards,PowerBookmarksSidePanel --disable-alternate-ds --popups-to-tabs

2. Notice the Windows error popup

Expected behavior Browser should work without errors. 122.0.6261.152 works but it has too strong restrictions for Google domains and I can not login with Google OAuth on various web sites (Figma, Postman, Notion, etc.) So I am currently stuck with 119.0.6045.192

Screenshots

Desktop (please complete the following information):

• OS: Windows 7 SP1 x64
• Supermium x64 124.0.6367.245

Additional context Don't know what to provide here. If you ask me more specific questions, I will answer.

[oleedd]

You are lucky that you could install. I have this on the same system:

[tmcdos]

I extracted the files manually from the installer - I always prefer to directly copy the files of any application I want to use on my PC rather than trusting an installer.

Hmm, it looks like I have accidentally enabled VxKex for Supermium. I was also experimenting with portable Chromium builds from Marmaduke whose newer builds refuse to run on Win7 without VxKex but even with it I observe weird behavior and had to stick with Supermium.

I disabled VxKex for Supermium 124.0.6367.245 and it seems to work fine for now. I am even able to login with Google OAuth on e.g. Figma and Notion - so it is great!

I will continue testing this version for a couple of days and if there are no other issues - I am going to close the issue.

[Jevil7452]

I am also facing this issue. I do not have VxKex enabled. Sometimes, I have to try launching the browser multiple times to get an usable session. But when I do, there's no issues.

[tmcdos]

I am using this version for the last 2 days (more than 10 hours per day) and I have not noticed other issues. I will continue using it daily.

[Darthagnon]

You are lucky that you could install. I have this on the same system:

I saw this error when I tried to install the Supermium v124 update on Win10 v1709, and I still had v122 open.

[Jevil7452]

Update about this issue: It seems more likely to occur for me when clicking on a link in another program while the browser is closed, or perhaps those have just been coincidences and it starts working when i go to open it normally?

[tmcdos]

@Jevil7452 Check that the browser does not stay in the background when you close it - I suspect this sometimes causes issues.

[Jevil7452]

I have this setting off. And whenever the error occurs, i execute tskill chrome which instantly closes all Chrome processes so they don't run in the background. I encountered this issue again just now, 3 times trying to open a link from inside of another app, the crash occured, i closed all processes always. Then I decided to open it normally from the shortcut, it worked fine.

[tmcdos]

I have to admit that I've never checked whether clicking on a link in another app will open Supermium - I always begin my day by starting Supermium from the shortcut icon, and then during the day copy-pasting the URLs instead of clicking on them.

[tmcdos]

Today is the first crash of Supermium v124 when opening the URL https://stackblitz.com/edit/tmcdos-compiler-core?file=src%2Fviews%2FFrontVariable.vue

Error code: RESULT_CODE_KILLED_BAD_MESSAGE

No matter how many times I restart Supermium, even when this URL is the only tab - it always crashes.