Bug 16593 - [iOS] monotouch-test ButtonBarItem test crashes on iPad 6.0.1 with llvmthumbsgen configuration
Summary: [iOS] monotouch-test ButtonBarItem test crashes on iPad 6.0.1 with llvmthumbs...
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 7.0.4.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-12-04 11:41 UTC by GouriKumari
Modified: 2016-05-24 20:53 UTC (History)
3 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 NOT_REPRODUCIBLE

Description GouriKumari 2013-12-04 11:41:36 UTC
Steps to reproduce:
Install Xamarin.ios 7.0.5 9c421594, corresponding mono
Execute monotouch test with llvmthumbsgen config

Actual result:
Button Bar Item test crashed on iPad2 6.0.1 device

Crash Report (Device log): https://gist.github.com/GouriKumari/a2f5f0234a48db3031cd

Log says: Application Specific Information:
monotouchtest[15472] has active assertions beyond permitted time: 
{(
    <BKProcessAssertion: 0x1f84ed70> identifier: Suspending process: monotouchtest[15472] permittedBackgroundDuration: 10.000000 reason: suspend owner pid:51 preventSuspend  preventThrottleDownCPU  preventThrottleDownUI 
)}
 
Elapsed total CPU time (seconds): 4.750 (user 4.750, system 0.000), 24% CPU 
Elapsed application CPU time (seconds): 0.002, 0% CPU

Is this device related?


Test Env:
OSX ML
iPad2 6.0.1
Xamarin.ios 7.0.5 9c421594
Comment 1 GouriKumari 2013-12-04 11:48:12 UTC
Updates to the above comment:

Test Env:
Xcode 4.6.3

Supplemental info:

Monotouch Test log: https://wrench.internalx.com/Wrench/WebServices/Download.aspx?workfile_id=178273

Build Log:  https://gist.github.com/GouriKumari/cd8f0bf4374e15ab2946
Comment 2 GouriKumari 2013-12-04 13:40:49 UTC
This bug could be related with a timeout issue in QA test script.  I will update the bug  with wrench test results.
Comment 3 GouriKumari 2013-12-04 16:21:11 UTC
Updates to  Comment #0:

In QA-monotouch master lane (bcb459864c609be42d15575dd35df920e57f0165), monotouch-test_llvmthumbsgen executes without any crash on the same ipad2 6.0.1 device.
Time taken by all tests included in ButtonBarItemTest is 11879 ms
Test Log: https://wrench.internalx.com/Wrench/WebServices/Download.aspx?workfile_id=1784113

However, in QA-monotouch7.0.5 lane (9c4215943e6e9027a1ab7f297c27c9b53e69838f), monotouch-test_llvmthumbsgen executes indefinitely (with no timeout) or crashes at ButtonBarItemTest, CustomView_NoUserReference (with timeout). Standalone execution of CustomView_NoUserReference on device takes 6141ms.

Test Env:
Xcode46
iPad2 6.0.1
Xamarin.iOS master: bcb459864c609be42d15575dd35df920e57f0165
Xamarin.iOS 7.0.5: 9c4215943e6e9027a1ab7f297c27c9b53e69838f
Comment 4 Sebastien Pouliot 2013-12-11 16:27:09 UTC
For some reason the app hung -> 0x000000008badf00d
but the original crash report is not symbolicated so it's not clear where exactly that happened.

Also wrench link for comment #1 does not work -> 500

Can you still duplicate the issue ? i.e. maybe the device was rebooted between your test on 7.0.5 and master. If it still happens please attach a symbolicated crash report.
Comment 5 GouriKumari 2016-01-12 22:34:39 UTC
This was a random failure that occurred in old iOS versions. I am moving the target milestone to  "far future".
Comment 6 Sebastien Pouliot 2016-05-24 20:53:08 UTC
Please re-open if you hit the issue again