This is happening because the MovieGl calls close() when the app's window closes, which destroys the MovieGl's internal state, yet the MovieGl's destructor hasn't been called yet. I hit this as I was trying to pause the video from my VideoView when shutdown began. However at this point, calling almost any of the MovieGl's methods will cause assertions to fire in debug and try to access a null mObj in release.
Maybe all those assertions aren't necessary, and instead the methods just don't do anything and return default values when mObj or mObj->mPlayerPtr don't exist (shutdown)?