Bug 3425 - New monotouch results in many "malloc: *** error for object 0x103bc1b4: incorrect checksum for freed object"
Summary: New monotouch results in many "malloc: *** error for object 0x103bc1b4: incor...
Status: RESOLVED DUPLICATE of bug 3522
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-02-13 11:50 UTC by Ian
Modified: 2012-02-20 17:53 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 DUPLICATE of bug 3522

Description Ian 2012-02-13 11:50:22 UTC
Hi,

I have a large stable code base of apps, but after I updated to the newest Mono/Monotouch I am getting a lot of these memory errors and have no idea where they are coming from:


BibleAndCom(17931,0xacd3f2c0) malloc: *** error for object 0x103bc1b4: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
BibleAndCom(17931,0xacd3f2c0) malloc: *** error for object 0x103bc1b4: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug


The next line is random, but the preceding lines happen a lot.

2012-02-13 08:44:05.147 BibleAndCom[17931:1207] -[UIWindow countByEnumeratingWithState:objects:count:]: unrecognized selector sent to instance 0x765a590
Comment 1 Ian 2012-02-13 12:03:33 UTC
Further to this. All my apps are crashing inthe simulator. Here's an other kind of strange error:

2012-02-13 09:00:44.480 TimeBible[18349:1907] -[UIStatusBarWindow convertPoint:fromLayer:]: unrecognized selector sent to instance 0x9b86b20

The status bar is hidden in this app and I do nothing with it.

This happens when I touch the screen.

This happens on apps that share no code at all. I have many customers so the only common item is that I am using the newest MT and MonoDevelop
Comment 2 Ian 2012-02-13 12:07:05 UTC
Here's the version list:
MonoDevelop 2.8.6.4
Installation UUID: 438ac2b5-07c9-45e7-a8ce-eac5ad86371d
Runtime:
	Mono 2.10.8 (tarball Mon Dec 19 17:43:18 EST 2011)
	GTK 2.24.5
	GTK# (2.12.0.0)
Mono for Android: 4.0.3.85258578 (Evaluation)
Apple Developer Tools:
	 Xcode 4.2.1 (834)
	 Build 4D502
Monotouch: 5.2.3
Build information:
	Release ID: 20806004
	Git revision: ca00645c0f884e6cab8e8794fc7d65b2f6f3e5c3
	Build date: 2012-01-27 21:13:18+0000
Operating System:
	Mac OS X 10.7.3
Comment 3 Rolf Bjarne Kvinge [MSFT] 2012-02-13 12:35:47 UTC
Which version of Xcode / iOS SDK do you have?

Have you tried clean & rebuild of the projects, and/or delete the bin and obj directories in the project directory?
Comment 4 Sebastien Pouliot 2012-02-18 11:17:33 UTC
Ian, a similar issue was discussed on the mailing-list and had to do with the version of the simulator being executed. Can you check if this same thing is occurring to you ? 

ref: bug #3522 (reported crash is different but it started with a similar one on the mailing-list).
Comment 5 Rolf Bjarne Kvinge [MSFT] 2012-02-20 17:53:48 UTC
Marking as duplicate of #3522 for now, if the issue still persists after the next MonoDevelop update, please reopen this bug.

*** This bug has been marked as a duplicate of bug 3522 ***