Skip to content
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

Constant NullReferenceException with Reduced Rates active #18

Open
joelspadin opened this issue Apr 13, 2015 · 4 comments
Open

Constant NullReferenceException with Reduced Rates active #18

joelspadin opened this issue Apr 13, 2015 · 4 comments

Comments

@joelspadin
Copy link
Contributor

When the company action Reduced Rates is active, I get repeated null reference exceptions in ActorEntityHelper.cs line 201. statusEntry.StatusID is 0, and StatusEffectHelper.StatusInfo() returns null.

@Icehunter
Copy link
Member

Is it only on reduced rates?

I have all the ID's setup and that one is here:

https://github.com/Icehunter/ffxivapp-common/blob/master/FFXIVAPP.Common/Helpers/StatusEffectHelper.cs#L4413

If the ID is wrong and doesn't exist though it should return a "???" as the info.

https://github.com/Icehunter/ffxivapp-common/blob/master/FFXIVAPP.Common/Helpers/StatusEffectHelper.cs#L64

What's the status ID when it hits here:?
https://github.com/Icehunter/ffxivapp/blob/master/FFXIVAPP.Client/Helpers/ActorEntityHelper.cs#L200

@joelspadin
Copy link
Contributor Author

Reduced Rates was the only buff/debuff up at the time, but after looking at it again, I don't think it's related to that specific buff.

The status ID was 0. StatusEffects did contain a key "0" which apparently had a value of null, as StatusEffects.ContainsKey(id) returned true. When I inspected StatusEffects with the debugger, it had a two or three keys with values of null at the beginning. I restarted the program, and StatusEffects no longer has those keys, so I am not sure what happened. It looks like StatusInfo() is called repeatedly with ID 0, and StatusEffects somehow got modified or corrupted.

Icehunter added a commit that referenced this issue Apr 13, 2015
JobIcon changes per PR #18
@Icehunter
Copy link
Member

Code-wise though it shouldn't do that; so it's a mystery to me right now. There's a lock on the array and zero never exists so it should always return a default unknown status.

I'll have to look at that more.

@joelspadin
Copy link
Contributor Author

I'll let you know exactly what the contents of StatusEffects look like if I see it happen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants