[Mono-bugs] [Bug 672503] New: Memory leak when repeatedly creating (and disposing of) bitmaps
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Wed Feb 16 08:01:14 EST 2011
https://bugzilla.novell.com/show_bug.cgi?id=672503
https://bugzilla.novell.com/show_bug.cgi?id=672503#c0
Summary: Memory leak when repeatedly creating (and disposing
of) bitmaps
Classification: Mono
Product: MonoDroid
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Runtime
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: matware at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: Beta-Customer
Blocker: Yes
Description of Problem:
In Preview 12, I ported the Sensors test application to C#. After running the
ported version I noticed it would crash after a while when the user switched
screen orientation.
The crash would either be a null reference exception on the
base.OnCreate(bundle) or an out of memory exception during the bitmap creation.
The attached application takes quite bit longer to crash than the demo
application was I attempted to make sure that everything that could be user
induced memory leak was removed.
Steps to reproduce the problem:
1. Build and deploy the attached solution to a device
2. Repeatedly rotate the device (60+ in some cases)
Actual Results:
The application will crash with an out of memory exception.
Expected Results:
I would expect the screen to continue to flip forever.
How often does this happen?
Always
Additional Information:
As a side note, it appears very very easy to generate memory leaks in monodroid
as lots of classes that are can be left to their own devices in Java need to be
disposed of in MonoDroid, and the Dispose method on Activity doesn't appear to
be called by the Destory method or anything else for that matter.
Link to Sensors.Java :
http://developer.android.com/resources/samples/ApiDemos/src/com/example/android/apis/os/Sensors.html
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list