Failure to launch on Windows 11

Logic 2 Software
1

I’m running Windows 11 on a ThinkPad P16s Gen 3 and an Intel Ultra 7 155H.
I’ve tried the latest version (2.4.44), 2.4.45-insider, and just for fun 2.2.5. The newer versions all fail to launch no matter what with this error message:

PS C:\Program Files\Logic> .\Logic.exe
PS C:\Program Files\Logic>
Environment
Executable path: C:\Program Files\Logic\Logic.exe
Executable directory: C:\Program Files\Logic
Original working directory: C:\Program Files\Logic
Current working directory: C:\Program Files\Logic
Process ID: 7552
Crash reporting enabled. Machine ID: d94de905-a8bc-4e9a-b563-6f4c45a1bb77. Upload to server: true
@saleae/electron/main: renderer process died { reason: ‘crashed’, exitCode: -1073741819 }

I’ve tried different flavors of --disable-gpu, --no-sandbox, --in-process-gpu and all generate the same crash and exitCode.

On the older version (2.2.5) the main UI will launch and then crash immediately when I connect my Saleae Logic 8.

Anybody have some advice about where to go from here? I’m stuck with a paperweight for now.

2

Sorry for the trouble with that! Can you also share 2 additional items below?

  1. Your crash logs:
    Getting your Software Crash Logs | Saleae

  2. Your console output when launching the software:
    Getting the Console Output | Saleae

Lastly, just to cover our bases, can you confirm you are downloading and running the x64 versions of our software?

3

Hi timreyes (Tim?),

Thanks for getting back to me.

My Windows console log is in my original post, see above for details. I’m out for a day or two and will plan to get the Software Crash Logs for you on Tuesday.

~Matt

4

Hi Tim,

I am running the Logic-2.4.44-windows-x64.exe installer to install the program.

Crash Log directories are generated but do not contain any log files:

Log File Directories
Log File Directories896×373 24.8 KB

No Log Files
No Log Files932×310 9.79 KB

Console output is the same as before from the console itself. If I try to use ‘>’ to send it to a file then the console output file generates but is empty. This is all with no Saleae hardware connected. I’m simply trying to launch the software by itself.

PS C:\Program Files\Logic>
Environment
Executable path: C:\Program Files\Logic\Logic.exe
Executable directory: C:\Program Files\Logic
Original working directory: C:\Program Files\Logic
Current working directory: C:\Program Files\Logic
Process ID: 45724
Crash reporting enabled. Machine ID: d94de905-a8bc-4e9a-b563-6f4c45a1bb77. Upload to server: true

/electron/main: renderer process died { reason: 'crashed', exitCode: -1073741819 }

PS C:\Program Files\Logic>
5

Did you try launching with --disable-gpu and/or --no-sandbox command-line options? If that works, are all your graphics drivers updated to latest?

On ThinkPad P16s Gen 3, I think there are known issues auto-switching between the built-in Intel/Arc and discrete NVIDIA GPUs. If that is it, you can try forcing the settings on running C:\Program Files\Logic\Logic.exe to Performance (NVIDIA) or Power Saving (Intel Arc) in Windows Settings ➔ System ➔ Display ➔ Graphics, too.

6

Hi BitBob,

As mentioned in my original post:

I’ve tried different flavors of --disable-gpu, --no-sandbox, --in-process-gpu and all generate the same crash and exitCode.

These flags to not change the behavior of the software in any way. It still crashes on each launch with the same error code.

7

My apologies, I missed that you’ve already tried those initial options. There were a few other combinations of command line flags, but the overall theme seemed to be around electron / chromium browser interactions with the GPU(s) and/or GPU drivers.

Ideas include:

  1. Confirm all your drivers are up-to-date (especially new Intel/Arc GPU)
  2. Clear the %AppData% cache for Logic
  3. Try the Windows compatibility mode(s) on Logic.exe process (as windows may use Arc GPU at OS level)
  4. Try additional electron options (including more debug/logging)
  5. Try enabling Windows error reporting, per suggestion in linked article
  6. Try disabling Data Execution Prevention (DEP) globally, or just for Logic 2 app
  7. Make sure anti-virus or other app overlays aren’t hooking into Logic app’s memory (disable and/or whitelist logic)

Additional Electron GPU disabling options:

  • --disable-gpu-compositing
  • --disable-software-rasterizer

Enhanced Electron debug/console logging options:

ELECTRON_ENABLE_LOGGING=1
ELECTRON_DEBUG_NOTIFICATIONS=1
ELECTRON_ENABLE_STACK_DUMPING=1

Log level: --log-level=0 or other [0..3]

  • 0: INFO
  • 1: WARNING
  • 2: ERROR
  • 3: FATAL

Verbose level: --v=1 --vmodule=*=1 or other [1..4] (4 is max verbose level?)

8

Thanks, BitBob - I’ll give these a try next week.