Bug 6611 - CMSampleBuffer Dispose() causes app to crash
Summary: CMSampleBuffer Dispose() causes app to crash
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-08-20 10:08 UTC by Kraig McConaghy
Modified: 2013-12-05 18:34 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 NORESPONSE

Description Kraig McConaghy 2012-08-20 10:08:06 UTC
When I created a AVCaptureVideoDataOutputSampleBufferDelegate, sometimes calling Dispose on the CMSampleBuffer will cause the app to crash.  Usually it crashes within a 15 seconds. At first I thought I was just doing something wrong but it happens with the monotouch AVCaptureFrames sample on github.  I have noticed that generally right before it happens there is a memory warning.
Comment 1 Sebastien Pouliot 2012-08-20 10:31:04 UTC
Please use MonoDevelop's main menu, then "About MonoDevelop" menu item,
"Version Information" tab and copy-paste the information from there. That will
the basics we need to know to try to duplicate the issue.
Comment 2 Kraig McConaghy 2012-08-20 10:47:09 UTC
MonoDevelop 3.0.3.5
Installation UUID: e2437e2f-673d-4394-83e3-7359643b0f7b
Runtime:
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.4.1 (1488)
	 Build 4F1003
Monotouch: 5.2.13
Mono for Android: 4.2.4.167234518 (Evaluation)
Android SDK: /Developer/SDKs/android-sdk-macosx
Supported Android versions:
	Version: 1.6	ApiLevel: 4
	Version: 2.1	ApiLevel: 7
	Version: 2.2	ApiLevel: 8
	Version: 2.3	ApiLevel: 10
	Version: 3.1	ApiLevel: 12
	Version: 4.0	ApiLevel: 14
	Version: 4.0.3	ApiLevel: 15
Java SDK: /usr/bin

Build information:
	Release ID: 30003005
	Git revision: 3d53e1366933298a3fe0cdc6d0f7d00c9916564c-dirty
	Build date: 2012-07-27 19:06:34+0000
	Xamarin addins: 73ecde7c48d943adb6e33d511d3cf0661d006801
Operating System:
	Mac OS X 10.8.0
	Darwin support2.smartcopinc.com 12.0.0 Darwin Kernel Version 12.0.0
	    Sun Jun 24 23:00:16 PDT 2012
	    root:xnu-2050.7.9~1/RELEASE_X86_64 x86_64
Comment 3 Sebastien Pouliot 2012-09-04 14:42:30 UTC
I cannot duplicate the issue with the latest MonoTouch code (iPod 4th and iPad 3rd gen) and the AVCaptureFrames sample. OTOH the description looked similar to an old bug (which is why I asked the version number).

We'll be releasing 5.4 (stable) shortly (and likely won't update 5.2.13). Could you see if it works with 5.3.6 (the latest beta) ?
Comment 4 PJ 2013-11-19 17:04:14 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 PJ 2013-12-05 18:34:14 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.