Bug 30239 - Receiving Memory Warning When Using Avcaptureframes
Summary: Receiving Memory Warning When Using Avcaptureframes
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Samples ()
Version: XI 8.10
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Rustam Zaitov
URL:
Depends on:
Blocks:
 
Reported: 2015-05-19 14:25 UTC by Jimmy [MSFT]
Modified: 2015-06-22 14:57 UTC (History)
4 users (show)

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


Attachments
Outputs (11.34 KB, application/zip)
2015-05-19 14:25 UTC, Jimmy [MSFT]
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 Jimmy [MSFT] 2015-05-19 14:25:46 UTC
Created attachment 11246 [details]
Outputs

*** Overview ***
When the camera is implanted using AVFoundation and AVCaptureSession, several memory warnings are thrown. Application output and build output attached.


*** Steps to Reproduce ***
1. Run the AV Capture Frames sample: https://developer.xamarin.com/samples/monotouch/AVCaptureFrames/
2. After the app has been running for a few seconds, the application output should show a memory warning. More warnings are thrown as the app keeps running.


*** Actual Results ***
Memory warnings are thrown which causes apps that implement this solution to crash.


*** Expected Results ***
No memory warnings.


*** Environment Info ***
=== Xamarin Studio ===

Version 5.9.2 (build 0)
Installation UUID: 94ce5106-6a72-4691-b34e-cd5857b1db66
Runtime:
	Mono 4.0.1 ((detached/6d5afc1)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400010034

=== Apple Developer Tools ===

Xcode 6.3.1 (7703)
Build 6D1002

=== Xamarin.Android ===

Version: 5.1.2.0 (Business Edition)
Android SDK: /Users/jimmygarrido/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.iOS ===

Version: 8.10.1.56 (Business Edition)
Hash: b39367d
Branch: master
Build date: 2015-05-14 08:50:11-0400

=== Xamarin.Mac ===

Version: 2.0.1.56 (Business Edition)

=== Build Information ===

Release ID: 509020000
Git revision: f97f3598952edca4678fc9fdafffecb68ed24399
Build date: 2015-05-08 11:55:56-04
Xamarin addins: ab18ddff45f507ed74f36c2b65df9aee22e28a56

=== Operating System ===

Mac OS X 10.10.3
Darwin Jimmys-MacBook-Pro.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 Atin 2015-06-04 11:29:06 UTC
I have checked this issue and able to reproduce the reported behavior with the help of sample and steps given in the bug description.

Screencast: http://www.screencast.com/t/4zbr5nSO
Ide Logs: https://gist.github.com/RamChBachkheti/684e625fba436c72c4b0
Application Output: https://gist.github.com/RamChBachkheti/262f1081bdd2cee526c6
Device Logs: https://gist.github.com/RamChBachkheti/4786a3753905e95150a9
Build Output: https://gist.github.com/RamChBachkheti/483f1b8cd183b9dded92

Environment Info:

=== Xamarin Studio ===

Version 5.9.4 (build 1)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
Runtime:
	Mono 4.0.1 ((detached/2a0f19e)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400010056

=== Apple Developer Tools ===

Xcode 6.3 (7569)
Build 6D570

=== Xamarin.iOS ===

Version: 8.10.1.66 (Enterprise Edition)
Hash: 14c4f03
Branch: master
Build date: 2015-06-02 01:21:42-0400

=== Build Information ===

Release ID: 509040001
Git revision: a4a0ff65f54cd4533883b8461ba800708853b6f0
Build date: 2015-06-03 06:17:49-04
Xamarin addins: c12ed369b0e05dc5c35c9350fdcbc00a46c0ff99

=== Operating System ===

Mac OS X 10.10.3
Darwin Dalvik.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 2 Rustam Zaitov 2015-06-22 14:57:02 UTC
Fixed. Available in master. The problem was that we didn't dispose previous image (GC frees the memory but after warnings)