WowAce

How to reproduce the problem:

First method:

1.  Set a diferent layout for solo and group.

2.  Enter WOD citadel provind grounds

3.  Start the combat.

4.  Right Click player portrait and choose leave instance in the menu.

5.  Player returns to the Citadel but unit frames (the player frame in this case) are not displayed.

Second method:

1. Set a diferent layout for solo and group.

2. Group with a friend or another account toon (for example a free trial account)

2. Goto near a dungeon entrance.

3. Start combat with some npc near the entrance.

4. Leave the group.

5. Enter in the dungeon while your toon is in combat.

Cause:

The player is removed from the group while in combat,  several GROUP_ROSTER_UPDATED are fired by the game and Grid2 tries to load the layout specified in config for Solo, but its not possible in combat, so the layout load is queued and delayed until the combat ends.

After a few milliseconds the combat ends (PLAYER_REGEN_ENABLED is fired) the layout is reloaded, but player unit does not exist at this point so SecureGroupHeaders code displays nothing.

Just After PLAYER_REGEN_ENABLED event the game fires a PLAYER_LEAVING_WORLD/displays load screen/PLAYER_ENTERING_WORLD, the unit player returns to existence, but GROUP_ROSTER_UPDATED or UNIT_NAME_UPDATED is not fired anymore , so blizzard SecureGroupHeaders code never updates the frames after the load screen.

Possible Workaround:

- Ignore the Layout Load if player unit does not exists, because if player does not exist probably we are changing instances and the layout will be reloaded soon in the upcoming PLAYER_ENTERING_WORLD event.

Implemented a workaround in version 1.1.5-alpha