Bug 32984 - App crash in recent Xamarin version
Summary: App crash in recent Xamarin version
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Other ()
Version: 2.4.0 (C6)
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2015-08-11 18:37 UTC by bugreporter
Modified: 2017-01-20 18:36 UTC (History)
4 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 NORESPONSE

Description bugreporter 2015-08-11 18:37:17 UTC
The application works in June 2 release, but crashes during runtime after upgrading to June 30 release or newer.


Including slightly stripped output from Aug 10 release:

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        
0x00007fff8a5e2286 __pthread_kill + 10
1   libsystem_c.dylib             
0x00007fff94f3db53 abort + 129
2   com.app.app.v1 
0x00000001000eccd2 mono_handle_native_sigsegv + 578
3   com.app.app.v1 
0x00000001000620ba mono_arch_handle_altstack_exception + 90
4   com.app.app.v1 
0x0000000100100774 mono_sigsegv_signal_handler + 436
5   libsystem_platform.dylib      
0x00007fff8ffa4f1a _sigtramp + 26
6   com.app.app.v1 
0x00000001001a1514 mono_object_unbox + 4
7   com.app.app.v1 
0x0000000100009af3 marshal_return_value + 1891
8   com.app.app.v1 
0x0000000100008f4b xamarin_invoke_trampoline + 6491
9   com.app.app.v1 
0x00000001000090e1 xamarin_arch_trampoline + 193
10  com.app.app.v1 
0x000000010000a5aa xamarin_x86_64_common_trampoline + 110
11  com.apple.AppKit              
0x00007fff92a92acd -[NSView _updateGeometryFlippedOnLayerBasedOnOldSuperview:] + 58
12  com.apple.AppKit              
0x00007fff92a8f8d1 -[NSView _setSuperview:] + 1628
13  com.apple.AppKit              
0x00007fff92b549e4 -[NSClipView _setSuperview:] + 153
14  com.apple.AppKit              
0x00007fff92abb07f -[NSView removeFromSuperview] + 435
15  com.apple.AppKit              
0x00007fff92b9bea9 -[NSView removeFromSuperviewWithoutNeedingDisplay] + 38
16  com.apple.AppKit              
0x00007fff92ad4798 -[NSView _finalizeWithReferenceCounting] + 1000
17  com.apple.AppKit              
0x00007fff92ad437e -[NSView dealloc] + 151
18  com.apple.AppKit              
0x00007fff92d6709c -[NSScrollView dealloc] + 652
19  com.app.app.v1 
0x000000010000741b invoke_objc_method_implementation + 59
20  com.app.app.v1 
0x0000000100007570 xamarin_dealloc_trampoline + 128
21  libobjc.A.dylib               
0x00007fff960d989c objc_object::sidetable_release(bool) + 236
22  com.app.app.v1 
0x000000010000741b invoke_objc_method_implementation + 59
23  com.app.app.v1 
0x00000001000073be xamarin_release_trampoline + 158
24  libobjc.A.dylib               
0x00007fff960bfe8f (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 575
25  com.apple.CoreFoundation      
0x00007fff95a9b6f2 _CFAutoreleasePoolPop + 50
26  com.apple.Foundation          
0x00007fff9815a762 -[NSAutoreleasePool drain] + 153
27  com.apple.AppKit              
0x00007fff92ad6cc1 -[NSApplication run] + 800
28  com.apple.AppKit              
0x00007fff92a53354 NSApplicationMain + 1832
29  ???                           
0x0000000106ddb221 0 + 4410159649
30  ???                           
0x0000000106ddaf15 0 + 4410158869
31  com.app.app.v1 
0x0000000100102d99 mono_jit_runtime_invoke + 1673
32  com.app.app.v1 
0x00000001001a15be mono_runtime_invoke + 110
33  com.app.app.v1 
0x00000001001a6dc8 mono_runtime_exec_main + 376
34  com.app.app.v1 
0x000000010005bcc7 mono_main + 7879
35  com.app.app.v1 
0x000000010000a970 main + 800
36  com.app.app.v1 
0x0000000100001254 start + 52

///////////////////////////////////////////////////////////////////////////////

Xamarin About:
=== Xamarin Studio ===

Version 5.9.5 (build 9)
Installation UUID: x 
Runtime:
	Mono 4.0.3 ((detached/d6946b4)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400030020

=== Apple Developer Tools ===

Xcode 6.4 (7720)
Build 6E35b

=== Xamarin.Mac ===

Version: 2.0.2.111 (Business Edition)

=== Build Information ===

Release ID: 509050009
Git revision: b99cb19a1d3b15d8980c4616f13f837457e5b292
Build date: 2015-07-28 02:01:44-04
Xamarin addins: d53d6eceb828422f3d4aff8547f2f6bab6c9ea58

=== Operating System ===

Mac OS X 10.10.3
MacBook-Air-2.local 14.3.0 Darwin Kernel Version 14.3.0
   Mon Mar 23 11:59:05 PDT 2015
   root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-08-12 03:40:58 UTC
Can you attach a test project we can use to reproduce this?
Comment 2 bugreporter 2015-08-12 12:35:48 UTC
We would have to make one and unfortunately we're fairly low on resources. 

Looks like it might be the garbage collector being overly aggressive. We can fix it on our end if we take an optimization hit by manually disposing of objects. Even that would be a lot of work though.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-08-12 12:42:20 UTC
We can work with your full project if it's fairly easy to reproduce.
Comment 4 bugreporter 2015-08-12 20:14:25 UTC
I don't think I'm at liberty to hand over the code base. I will look into getting a test project going.
Comment 5 bugreporter 2015-08-13 16:27:25 UTC
It appears to be table related. The table cell is being garbage collected. When we call something like TableReload() with a bunch of data, the table is no longer there.

Still working on getting approval to spearheading an effort to make the test app.
Comment 6 Timothy Risi 2017-01-20 18:36:41 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!