Geek asks and answers

Monotouch Crash app without StackTrace or logs (Destructor never called)

My MonoTouch app continues to crash, and I don't know what to do. At the moment, I feel like I've tried everything. I have a RootViewController that jumps to an infinite number of vewcontrollers. Each time a switch occurs, I manually call the utility on the previous ViewController and display a new one.

It seems like a memory leak for me, as the application resets about 20-40 ViewControllers and definitely becomes more sluggish before starting work.

  • How can I view the memory usage of my MonoTouch application on the device? (Not a crash in the simulator)

  • Any more diagnostic ways to find out why it crashes?

Any help would be greatly appreciated.

UPDATE I have added the following to my VC.

~TargetPromptController(){
    Console.WriteLine("TargetPromptController Released from memory!");
 }

And he never gets called.

+3
source share
2 answers

The C # GC class may give you an indication of the total amount of memory used, but it is very inaccurate and mostly incorrect. However, it can be said whether memory consumption is increasing, decreasing or stable. As a rule, I had more problems executing GC.Collect than I had. Therefore, my general assumption is not to use this method.

You can debug the device using the methods described here . However, I had a problem with this, and we recommend contacting Monotouch if you have problems debugging the device.

, , Monotouch ViewController , Dispose. List VC. MonoTouch VC. , VCs , . , Monotouch , .

, Monotouch , . , , !:)

0

, . , mono touch - , . GC , . . !

+1

More articles:


All Articles