Skill dropdown crash

[Nightblade]

Check version

• I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

• I've checked for duplicate issues by using the search function of the issue tracker

Screenshots of crash/graphical issue, version and options menu

What are your system specifications and configuration?

Win10

How to reproduce the issue

1. Click on the Vaal Ice Shot group (in the Skills tab)
2. ctrl+c & ctrl+v to duplicate the group,
3. Click Include in Full DPS on the new group,
4. Click on the old group,
5. Click on the empty skill slot (below Added Cold Damage),
6. Error popup 🥓

Character build code

https://pobb.in/jXCrnzwUSVBG

[RecurringNightmare]

yes, same issue here

the bug actually has a history
in the last days i noticed that the damage calculation for my selected main skill would confuse my first galvanic arrow skill group for self-use (trinity/mirage archer) and my second skill group that also has galvanic arrow but this time with ballista support
the drop-down would still show both skill groups and let me select them and if i wanted arrow or cone calculation, but both calculated for the totems and not for me attacking myself
deleting all skill groups and starting fresh solved that
now this new issue happens and it also has to do with two skill groups having the same skill gem and the main skill selection confusing them, apparently entering a loop and creating an overflow

in other words, if you have two skill groups that have the same skill gem and one of them is your selected main skill on the top left, trying to get the support gem dropdown list to show will likely produce the crash, although i just managed to get it to work normally for a minute, just to have the crash then happen again

if you make a totally different skill the main skill you can still work on your build, full dps etc still get calculated normally on the bottom left, just the details for the main skill on top left obviously are missing/wrong then...

hope they get it fixed soon, really annoying...

[Peechey]

Looks like this is caused by something introduced in 2.28.0 as I'm not able to reproduce the crash using these steps on 2.27.2

[Paliak]

It's caused by @Nostrademous 's implementation of Manaforged arrows. Fix on the way.