Monogame blocks / consumes Keyboard Input, how to disable this?

HappySoftwareDevelop · June 29, 2015, 10:04am

I think it is related to my post (first post is related to second where they are looking into it):

Dispose resources not working correctly

opened 08:00AM - 25 Jun 15 UTC

Hi everyone, Detection: Problem occured when ported from XNA to Monogame Back…ground: We recently ported our application from XNA to Monogame to be able to leave .NET4.0 and continue use the latest released (.NEt4.5). We have a WinForm application where you can start a XNA/Monogame where we have an animation that just illustrate a flow. XNA implementation: When the animation was done we exit the application pressing 'Esc' and two code of lines was used: this.Dispose() this.Exit() Monogame implementation: I can't use same implementation as for XNA since the line "this.Dispose()" make it crash later. I only use "this.Exit()". The game is started from an using statement: using (Demo d = new Demo()) d.Run() Error: If I try to start Monogame the second time and so on, Keyboard.GetState() is always empty and the memory is increasing for each time i start it. I think the problem is that objects/resources arn't disposed correctly, even when its started from an using statement. This will make the application grow until it crash and the user can't use keyboard inputs after the first time. I made a small .sln project to demostrate the problem: http://s000.tinyupload.com/download.php?file_id=05943256822998486463&t=0594325682299848646326883