Running the launcher produces a suitable Minecraft app icon on the Mac task bar. Selecting a particular dev release, logging in and clicking play, currently reliably causes a 'launcher error 139', 'Invalid memory access of location 0x0 rip=0x0'. This is already logged as MCL-90, and is a known problem with Mac Os 10.5.8.
But in addition, after the error, the launcher itself loses its icon, even though it's still running OK.
To reproduce, trying adding and running a borked version of Minecraft itself to the launcher; on Mac OS 10.5.8 every version does this; on other OSes you'd probably need to deliberately break something.
Attachments
Comments 7
No, everything is where MinecraftDev put it. I have been updating regularly even though I can't yet play any of the new snapshots. For example, I can try to start, say, 13w25a, which dies with error 139 as reported in MCL-90. But the launcher stays open, even though its icon has disappeared. I can then choose some other release, 13w20a, say, try to launch that, fail, try another and so on forever. So the /launcher/ is working throughout, save for the fact that it loses its icon the moment the main game suffers a launch error. It even continues to obtain updates correctly, even after losing its icon.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Why was this marked as /invalid/? Should have been 'unable to reproduce'. In any case, there is still a problem - on 1.6.2 and launcher 1.1.3 (IIRC), I don't get an icon at all.
This attachment is with the game (nothing), the launcher(generic Java app icon), and a minimised Minecraft window (OK). (JIRA annoyance: Why aren't comments on attachments visibly related to the attachments concerned? Gets me almost every time)
Are you running the snapshot in a different directory?