These sound like Mono bugs to me, it is issues like this that prevent me from recommending hosting any important production sites on Mono. I would not want to have 10 customer sites running on Mono myself because there are always some issues like this that I cannot solve because they are not issues in mojoPortal code. It can be reported to the Mono team but unless it is possible to come up with a simple test case that proves the issue (which is usually not easy to do) or at least easy repeatable steps they can use to produce the issue with mojoPortal then it is hard to get things fixed and in the best case you have to wait for the next release of Mono for the fix. And then the next release of Mono usually has some new issues or regressions along with the fixed things. It can be very stressful and difficult to provide customer satisfaction having important sites running under these circumstances.