1. We have a QA initiative where we work with the community more closely than ever to get your bug reports into the hands of the developers. Please use this forum for LIVE Server bug reporting. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

    Read BEFORE submitting your first bug: Reporting Bugsā€¦ QA 101 Document
    • Search for your bug before posting in order to avoid duplicate reports.
    • Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
    • Keep your bug report short and factual.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    Bug Report Template
    1. Title:
    2. Reproduction Rate:
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs:
    To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!
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:
    626
    Likes Received:
    563
    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.