Bug 7586 - Duplicate Console.WriteLine output
Summary: Duplicate Console.WriteLine output
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.2.x
Hardware: PC Mac OS
: Normal trivial
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2012-10-02 10:41 UTC by Chris Hardy [MSFT]
Modified: 2017-06-27 02:12 UTC (History)
3 users (show)

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:

Description Chris Hardy [MSFT] 2012-10-02 10:41:44 UTC
Using the following code:

Console.WriteLine ("Ordnance = {0}", count);

Produces the following output:

Ordnance = 878Ordnance = 878
Aircraft = 1033

Aircraft = 1033

1. If I start with the application not installed, or if MonoDevelop does 
a reinstall of the application, then the output is fine, no duplication.
2. If I run the application, then terminate it from MonoDevelop, then 
run again, the console output is duplicated.

So I think the duplicate console output is just an artifact from 
multiple runs of the same application on the same device, but otherwise 
does not appear to cause any issues with the execution itself.
Comment 2 Chris Hardy [MSFT] 2017-06-27 02:12:40 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.