Bug 3942 - When the updater re-opens MD, it creates a new dock icon.
Summary: When the updater re-opens MD, it creates a new dock icon.
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Updater ()
Version: 2.8 beta 3
Hardware: PC Mac OS
: --- minor
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-03-16 15:59 UTC by PJ
Modified: 2012-04-12 06:32 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description PJ 2012-03-16 15:59:58 UTC
I used the updater to switch branches from Beta to Stable. (2.8.8.1 to 2.8.6.5)

When MD went to re-open, a second dock icon appears.

The second dock icon, once closed, does not re-appear (you can use the old icon, the one locked to the dock, as normal to open and control MD)


This hasn't seemed to have any effect beyond the aesthetics, so marking it as trivial.

http://screencast.com/t/QMoMhbRcMs2 
^SS of double dock icon.
Comment 1 PJ 2012-03-19 15:38:15 UTC
This has slightly more annoying behavior than I had previously reported.

When this happens, I have to force quit the second instance. 

Bumping from trivial to minor.
Comment 2 Mikayla Hutchinson [MSFT] 2012-03-27 18:02:45 UTC
Is there any way to reproduce this on demand? Perhaps the old MD hung on exit, so both the old and new ones are running. Could you get a stacktrace from the hung MD?
Comment 3 PJ 2012-03-27 18:58:13 UTC
I will try to make this happen reliably and get the stacktrace. I saw this behavior today once only on Snow Leopard and not at all on Lion during my updater testing, so it's intermittent. 

Sorry for not grabbing the trace when I filed, should have done that. I imagine I was deep down another rabbit hole and felt the need to record the behavior at least.
Comment 4 PJ 2012-04-11 13:48:01 UTC
I just saw this issue again upgrading from:

MT 5.2.11
MD 2.8.8.4
MFA 4.0.6

to the current alpha channel
MT 5.3.2
MD 2.9.4
MfA 4.1.0 

After 'kill -QUIT', the log in console was useless.

Gonzalo showed me how to use GDB to get the stacktrace:

https://gist.github.com/2360860


Hope this helps!
Comment 5 Mikayla Hutchinson [MSFT] 2012-04-11 15:21:52 UTC
Looks like the iPhone USB debugger connection's CFRunLoop.
Comment 6 Rolf Bjarne Kvinge [MSFT] 2012-04-12 06:32:52 UTC
This happens if you're debugging an iOS app on device, the app crashes and then try to update.

Fixed in 154ab8587fb (md-addins master).