Bug 33789 - disable debugtrack for simulator profiling
Summary: disable debugtrack for simulator profiling
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: master
Hardware: PC Mac OS
: Normal normal
Target Milestone: (C7)
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
: 38144 ()
Depends on:
Blocks:
 
Reported: 2015-09-08 12:51 UTC by Rodrigo Kumpera
Modified: 2016-01-28 19:25 UTC (History)
6 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 Rodrigo Kumpera 2015-09-08 12:51:07 UTC
The frequent GC (every 1 second) on the simulator makes it quite hard for very long profiling sessions.

The problem is that each GC, even when not producing a heap dump, it collects quite some data.
Comment 1 Rodrigo Kumpera 2015-09-08 12:52:49 UTC
It would be nice to get this fixed for C7.

Even better if the fix lands in a C6 service release.
Comment 2 Rodrigo Moya 2015-09-22 10:10:54 UTC
Already discussed by mail, so adding it here for reference: apart from disabling it in x.ios, would the IDEs need to pass --nodebugtrack to mtouch when building/deploying?
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-09-22 13:16:39 UTC
--nodebugtrack is a temporary workaround until this has been implemented.
Comment 4 Miguel de Icaza [MSFT] 2015-09-23 15:40:28 UTC
Rolf, what would be the implementation be?

To do --nodebugtrack implicitly when some other flag is enabled?   If so which?
Comment 5 Rolf Bjarne Kvinge [MSFT] 2015-09-24 06:58:53 UTC
@Miguel, the implementation would stop the GC.Collect loop when a profiler is attached (this is done at runtime, so that the app doesn't have to be rebuilt).
Comment 6 Rolf Bjarne Kvinge [MSFT] 2015-11-16 08:28:44 UTC
Fixed.

maccore/master: 485a48879e0b62b5192775c746f66c94c4f53e1a
Comment 7 Rolf Bjarne Kvinge [MSFT] 2016-01-28 19:25:35 UTC
*** Bug 38144 has been marked as a duplicate of this bug. ***