Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

This morning's OS X Launcher update required a reboot

Discussion in 'Critical Issues (Blockers, Performance, Crashes)' started by Widsith [MGT], Feb 1, 2019.

  1. Widsith [MGT]

    Widsith [MGT] Avatar

    Messages:
    643
    Likes Received:
    579
    Trophy Points:
    93
    This morning's Launcher update (#146) did not go smoothly. When it first ran, it left two copies of the Launcher in the dock, both frozen and had to be force quit. After that, running the Launcher resulting in an icon bouncing forever in the dock, and not starting up the app. The only way to clear this was a shutdown. A soft shutdown from the Finder failed, and never completed. A hardware shutdown was required to get to a reboot. After the reboot, the first run of the Launcher succeeded, and again appeared to do the version 146 update. This one apparently ran correctly, and relaunched itself to do the game update.

    This isn't the first time I've seen flaky behavior when the OS X launcher is updated, but since it required a reboot, maybe it's time to actually debug the thing? The outgoing copy is apparently not ending correctly under some conditions, and leaving conditions that prevent the new copy (and the OS) from behaving correctly.