Mac desktop builds can only be run once #85

New Issue

claunia · 2026-01-29T16:30:16Z

claunia commented

2026-01-29 16:30:16 +00:00

Originally created by @yoDon on GitHub (Nov 29, 2017).

Originally assigned to: @robertmuehsig on GitHub.

It looks like running OSX builds of the app causes the app to modify itself and breaking itself somehow.

Here's what I'm seeing:

build full desktop OSX app
before running the app, make a copy of the app
run the app, close it, kill the zombie child process (per this issue), and run the app a 2nd time

Expected behavior: App runs the same both times
Actual behavior: App runs normally the first time, fails to show or populate window the 2nd time
Additional info: If you run the app from the commandline, you can see that the initial host processes are dumping less info to the command line on the 2nd run than on the first run but not reporting errors

if needed, kill zombie child process
run the copy of the app

Expected behavior: Running the app shouldn't mutate the app, so the original and copied versions of the app should behave the same (eg. the copy shouldn't run if the original app no longer runs)
Actual behavior: The copy of the app runs once, then fails to run, demonstrating that running the app modifies the app

Originally created by @yoDon on GitHub (Nov 29, 2017). Originally assigned to: @robertmuehsig on GitHub. It looks like running OSX builds of the app causes the app to modify itself and breaking itself somehow. Here's what I'm seeing: 1. build full desktop OSX app 2. before running the app, make a copy of the app 3. run the app, close it, kill the zombie child process ([per this issue](https://github.com/ElectronNET/Electron.NET/issues/68)), and run the app a 2nd time - Expected behavior: App runs the same both times - Actual behavior: App runs normally the first time, fails to show or populate window the 2nd time - Additional info: If you run the app from the commandline, you can see that the initial host processes are dumping less info to the command line on the 2nd run than on the first run but not reporting errors 4. if needed, kill zombie child process 5. run the copy of the app - Expected behavior: Running the app shouldn't mutate the app, so the original and copied versions of the app should behave the same (eg. the copy shouldn't run if the original app no longer runs) - Actual behavior: The copy of the app runs once, then fails to run, demonstrating that running the app modifies the app

claunia added the bug label 2026-01-29 16:30:16 +00:00

claunia closed this issue

2026-01-29 16:30:17 +00:00

claunia commented

2026-01-29 16:30:18 +00:00

@BrianAllred commented on GitHub (Nov 30, 2017):

Seeing the same behavior on Linux (although no zombie process for me).

@BrianAllred commented on GitHub (Nov 30, 2017): Seeing the same behavior on Linux (although no zombie process for me).

claunia commented

2026-01-29 16:30:18 +00:00

@Jonatthu commented on GitHub (Feb 18, 2018):

@robertmuehsig I have the same issue as him still in the latest update until today

@Jonatthu commented on GitHub (Feb 18, 2018): @robertmuehsig I have the same issue as him still in the latest update until today

claunia commented

2026-01-29 16:30:19 +00:00

@aguedob commented on GitHub (Mar 16, 2018):

Same issue here

@aguedob commented on GitHub (Mar 16, 2018): Same issue here

claunia commented

2026-01-29 16:30:19 +00:00

@GregorBiswanger commented on GitHub (Sep 26, 2018):

Fixed with the new version of Electron.NET.

@GregorBiswanger commented on GitHub (Sep 26, 2018): Fixed with the new version of Electron.NET.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#85