-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mod compatibility checker - null issue #386
Comments
Log file containing the error: |
It's not an issue with Linq, it's an issue with the code in Just |
@aubergine10, just curios: "Mac has known issues with Linq". Can you provide some links proving that? As far as I know, there are no issues with Linq implementation in Mono, neither on Mac nor on any other supported platform. |
@dymanoid, Is it possible? Just curious. I can see that I will check that anyway 😉 BTW I would like to see more info about issues with Linq too. |
@dymanoid It was something @VictorPhilipp mentioned ages ago, specifically that it caused major performance issues on Macs (from very vague memory it was used in the savegame serialisation code). In any case, I'll add the null checking on that |
I'm not sure the "massive performance issues" on Mac were caused by Linq. Rather by an inappropriate Linq usage 😄 @VictorPhilipp, can you give a particular example where Linq causes performance drop on Mac only? This is a very interesting topic. @krzychu124, that field indeed can be null. The call into your code comes from |
Subaru had this error on the mods incompatibility checker (LABS prior to PR #333) - only happened one time, I'm unable to reproduce it.
However, I'll add some try/catch wrappers to the updates in #333 so future errors won't impact end-users.
Note: Mac platform - Mac has known issues with Linq, we should avoid Linq wherever possible. I'll try and rip out the Linq code from #333 - it's only used in one place IIRC, a
.last()
somewhere.The text was updated successfully, but these errors were encountered: