Calculator: Crash occurs upon opening an additional session of Calculator that is not the same size and mode of the current, open session

[MicrosoftIssueBot]

Describe the bug
Crash occurs upon opening an additional session of Calculator that is not the same size and mode of the current, open session

Steps To Reproduce

1. Launch a session Calculator in Standard mode with History/Memory panel not displayed
2. Leave this 1st session open throughout the rest of the steps
3. Open a 2nd session
4. Resize the 2nd session to display History/Memory panel
5. Switch the 2nd session to another mode of calculator such as Scientific
6. Close the 2nd session
7. Open a 3rd session
8. If the mode of the third session reverted to the same mode of the 1st session, change the mode of the 3rd session to the mode that 2nd session was before it was closed
9. Close the 3rd session
10. Open 4th a session (if crash does not occur open and close additional sessions)

Expected behavior
Calculator doesn't crash

Device and Application Information

• Application Version: 10.2005.23.0

Additional context
Repro rate: 50% to 75%

Requested Assignment
I'm just reporting this problem. I don't want to fix it.

[MicrosoftIssueBot]

This is your friendly Microsoft Issue Bot. I created this issue automatically as requested by a team member.

[ghost]

@grochocki Yes, this issue also occurs on my PC.

[xuhongxu96]

The repro steps can be simplified to:

1. Ensure the 1st instance of Calculator is opened in Standard mode.
   i.e. If not, switch it to Standard mode, close it and reopen it.
2. Open the 2nd instance and it should be in the same mode (Standard) as the 1st instance.
3. Switch the 2nd instance to Scientific or Programmatic mode and then close the 2nd instance.
4. Open the 3rd instance and crash happens.
5. If crash doesn't happen, close the 3rd instance, switch the 1st instance to Scientific mode and crash happens.

The window size doesn't matter.
The repro rate is nearly 100%.

The issue can be worked-around by removing conditional namespace in XAML.
More like a bug in UWP.