I think you seem to understand that is not a Mono issue, but a MonoGame issue. Are different things, right? Also, it appears if you read the bug report, that there is a resize issue that happen all time because of a change in the MonoGame framework (not in Mono!)
Originally Posted by narciso
Thanks goodness that the bug report gave a profile file, so we also can check how much time is asked for various operations. I tried with my best understanding to see what is slow on this bug:
So excluding the Sleep call (which doesn't use CPU), that is used here and there, for 4 seconds, most of calls are in OpenGL/X11 stack.
3476 milliseconds (wrapper managed-to-native) OpenTK.Platform.X11.Functions:XGetWindowProperty (intptr,intptr,intptr,intptr,intptr,bool,intptr,intptr&,int&,intptr&,intptr&,intptr&)
4050 milliseconds (wrapper managed-to-native) System.Threading.Thread:Sleep_internal (int)
238 milliseconds OpenTK.Graphics.GraphicsContext:get_CurrentContext ()
270 milliseconds OpenTK.Graphics.GraphicsContext:<GetCurrentContext>m__6 ()
107 milliseconds OpenTK.Graphics.GraphicsContext:get_IsCurrent ()
204 milliseconds OpenTK.Platform.X11.X11GLContext:get_IsCurrent ()
298 milliseconds OpenTK.Platform.X11.XLock:.ctor (intptr)
232 milliseconds: OpenTK.Platform.X11.XLock:Dispose ()
I understand, is Mono's fault anyway, but is just for no reason!