Bug 41391 - Random application crash after long operation with my Xamarin.MAC application
Summary: Random application crash after long operation with my Xamarin.MAC application
Status: RESOLVED ANSWERED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: MSBuild ()
Version: 2.9.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2016-05-31 10:52 UTC by Alain
Modified: 2016-06-01 12:57 UTC (History)
1 user (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 ANSWERED

Description Alain 2016-05-31 10:52:53 UTC
Hello,

by installing version 2.9 of Xamarin.MAC, I see that it is more stable but I still had a few random crashes.

Through testing, I noticed that these crashes always come after a long operation. That is to say, I display a window and ongoing research for example via a webservice (lasts 10 to 15 seconds). I close and oops, that crash. Sometimes it crash directly in the search, sometimes by clicking the "Close" button.

Are there not something to do when launching a long process because I have the impression that crashes are of the objects that are no longer in memory while I have the window in front of me during the search operation and I close it.

I do not know, an option to add to the mmtouch ?

Alain
Comment 1 Chris Hamons 2016-05-31 14:44:56 UTC
@Alain

Bugzilla is the place for reporting defects and issues that are (at least somewhat) reproducible and actionable. Since your report contains no example showing the problem, nor steps to reproduce, and no stack trace, it is not actionable.

You can try to flush out GC related issues (or make them more reproducible) by running this code one time in your program:

new System.Threading.Thread (() => 
{
while (true) {
System.Threading.Thread.Sleep (100);
GC.Collect ();
}
}).Start (); 


I will be closing this bug for those reasons. Please feel free to post on our forums (http://forums.xamarin.com/categories/mac) or as you appear to have an existing business support license http://xamarin.com/support.
Comment 2 Alain 2016-06-01 07:47:27 UTC
I have 2 problems. I still have the problem with 2.9

I am trying to replicate the slows down the rendering in a small application but it is not easy of course. When you do X times something, and you do not know why it crashes when you close a window, I really do not understand.

2 mistakes I see regularly:

Crashed Thread: 16 Dispatch tail: NSOperationQueue 0x7f9c4603d240 :: NSOperation 0x7f9c46e2c9e0 (QOS: USER_INTERACTIVE)
 
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
 
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '*** - [{NSMapTable NSMapTable
}
] Count underflow '
terminating with uncaught exception of types NSException
abort () called Expired

Thread 16 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x0000700000093738 rdx: 0x0000000000000000
  rdi: 0x0000000000004b4b RSI: 0x0000000000000006 rbp: 0x0000700000093760 rsp: 0x0000700000093738
   r8: 0x0000000000000000 R9: 0x0000000000989680 r10: r11 0x000000000c000000: 0x0000000000000206
  r12: r13 0x00007000000938f0: 0x0000000000000000 r14: r15 0x0000700000094000: 0x00007000000937d0
  rip: 0x00007fff98505f06 rfl: 0x0000000000000206 a2: 0x00007f9c3b81900c

and

Awake Time Since Boot: 600000 seconds
 
System Integrity Protection: enabled
 
Crashed Thread: 18 Dispatch tail: NSOperationQueue 0x7fc773073350 :: NSOperation 0x7fc7731a3470 (QOS: USER_INTERACTIVE)
 
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
 
VM Regions Near 0:
->
    __TEXT 000000010c914000-000000010ccf3000 [3964K] r-x / MS = rwx COW /Applications/Medinect.app/Contents/MacOS/Medinect
 
Application Specific Information:
objc [7911] NSWindowGraphicsContext object 0x7fc7728545f0 overreleased while already deallocating; break it to debug objc_overrelease_during_dealloc_error
abort () called Expired
Comment 3 Alain 2016-06-01 09:30:20 UTC
I was able to reproduce the problem in a small application. I sent to the support. I'll wait for their answer.
Comment 4 Chris Hamons 2016-06-01 12:46:19 UTC
See my note before. This bug is still not reproducible currently, nor does it contain much beyond "I'm seeing some crashes on this app you don't have".

Bugzilla reports are not the place to request assistance.

I'll take a look at your forum post. Support can open a new, complete, bug if necessary.
Comment 5 Alain 2016-06-01 12:57:51 UTC
I expect the support and see what they say. I guess if they see that this is a bug, they will report.