Microsoft/calculator

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

Open

#1340 opened on Aug 6, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (16,196 stars) (2,422 forks)batch import
Area: ReliabilityBugPri: 2help wantedtriage approved

Description

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.

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C++Windows programmingCalculator codebase understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by reproducing the crash using the provided steps. Then examine the session management code (likely in a class managing calculator sessions) to understand how new sessions are created and how mode and size changes are persisted. Look at the code that handles session close and subsequent opening to identify potential state corruption. Check any comments on the issue for additional hints.