SFML community forums

Bindings - other languages => DotNet => Topic started by: netrick on July 16, 2015, 04:04:25 pm

Title: SFML.Net performance (GC)
Post by: netrick on July 16, 2015, 04:04:25 pm

I have a question related to the following issue: https://github.com/SFML/SFML.Net/issues/5 (https://github.com/SFML/SFML.Net/issues/5).

I see it's still not fixed, so I'm wondering if there are some problems related to performance/stuttering/memory usage using this binding?
I am asking about both Microsoft CLR (Windows) and Mono (Linux).

Thank you

Title: Re: SFML.Net performance (GC)
Post by: netrick on July 17, 2015, 12:48:41 pm

I want to clarify one thing. I'm not asking about some very advanced technical stuff and theorycrafting - I just want to know if you had any problems in more advanced SFML.Net projects. Using "hello worlds" etc. everything seems to work fine, altough I have no idea how it looks like in more demanding scenarios.

Title: Re: SFML.Net performance (GC)
Post by: zsbzsb on July 18, 2015, 02:30:38 pm

Quote

I just want to know if you had any problems in more advanced SFML.Net projects.

No, there is not any problems. As for the actual open issue on the tracker I'm starting to consider it a non issue. The only thing it would change is if someone would let an SFML.Net object go out of scope without explicitly calling .Dispose() on the object. And if the person isn't calling .Dispose() then you will have no idea when the GC gets around to destroying the object and thus it can seem as if a memory leak is happening.

http://stackoverflow.com/questions/2548664/do-i-need-to-call-dispose-on-managed-objects