Bug 25512 - Infinite GC_MINOR / GC_OLD_BRIDGE errors (Nursery Full)
Summary: Infinite GC_MINOR / GC_OLD_BRIDGE errors (Nursery Full)
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-12-18 16:14 UTC by Ian
Modified: 2016-03-25 19:06 UTC (History)
4 users (show)

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


Attachments
screen shot fo GC errors - Android (380.52 KB, image/jpeg)
2014-12-18 16:14 UTC, Ian
Details
Build Info (4.10 KB, text/plain)
2014-12-19 12:12 UTC, Ian
Details
xam logs (17.09 KB, application/x-zip-compressed)
2014-12-19 12:16 UTC, Ian
Details


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 Ian 2014-12-18 16:14:48 UTC
Created attachment 9134 [details]
screen shot fo GC errors - Android

In our Android Forms app, we run into this error often, can't determine what is causing it. The attached screen shot shows the LogCat. What you see is the same over and over again infinitely, the scrolling never stopped with the same GC errors. 

Visual Studio becomes unresponsive as well, it has to be killed with Task Manager.
Comment 1 Ian 2014-12-18 16:31:38 UTC
Some more info:

I narrowed the error to my call to:

     var choice = await DisplayActionSheet(Words.Select, Words.OK, Words.Cancel, GetAccounts());

If I changed it to:

     _accountList = GetAccounts(); //!!!!PULLED IT OUT!!!!!!
     var choice = await DisplayActionSheet(Words.Select, Words.OK, Words.Cancel, _accountList );

and made _accountList a class level variable, then it works.


Where GetAccounts() is just a simple method:


        public string[] GetAccounts()
        {
            return new[]
            {
                Words.All,
                Words.Statements,
                Words.Tax_Statements,
                Words.Trade_Confirmations
            };
        }
Comment 2 Ram Chandra 2014-12-19 06:06:04 UTC
I can't reproduce this, we may have to see if a developer can figure out what's going on here. If you have a chance, it might also be helpful to include sample application, build info, IDE and device logs.

You can provide required info form here:

1. Build Info:  
Open Visual Studio=> Help=> About Microsoft Visual Studio => Copy Info 

2. For  IDE logs:
Open Visual Studio=> Help=> Zip Xamarin Logs 

3. For device logs:  Adb logcat/device logcat

Environment Info:

Windows 8.1
Xamrin.Forms: 1.2.3 / 1.3.0.0

Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Version 4.5.50938
Installed Version: Professional
Xamarin   3.8.150.0 (10cfd178d55287f09c85f5a1e604dfe20889a40f)
Xamarin.Android   4.20.0.28 (ba9bbbdd44cfdc4bf485e8885bd2ad24fba525f7)
Xamarin.iOS   8.4.0.0 (840a925103a0bf4a856507f13d5eaee3c1579c2f)
Comment 3 Ian 2014-12-19 12:11:46 UTC
See attached
Comment 4 Ian 2014-12-19 12:12:42 UTC
Created attachment 9143 [details]
Build Info
Comment 5 Ian 2014-12-19 12:16:24 UTC
Created attachment 9144 [details]
xam logs
Comment 6 Jason Smith [MSFT] 2016-03-25 19:06:09 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
 
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team