When I close the MacBook display and reopen it, the IDE (2.3.6) arbitrarily clears the output tab and serial monitor, and it's the same as when I started it.
If this is the intended function, I think it would be like deleting user information without permission, which is unacceptable.
I reverted back to 2.3.4 and hope this issue will be fixed.
My environment
MacBook Pro (Intel Mac) / MacOS 11.7.10(Big Sur)
Arduino IDE 2.3.6
Before closing display
After opening display
(note: I skipped to update "ESP32 by Espressif v3.2.0". Therefore, a dialog prompting to update the board package will be displayed at startup.)
What exactly do you mean by
What actions are you performing to do this ?
My Mac does the same thing.
Thanks for the feedback, we're tracking the issue here
opened 11:50AM - 10 Apr 25 UTC
type: imperfection
### Describe the problem
When the operative system re-activate from sleep mode,… the IDE seems to perform a reload (loading logo is shown) and current changes in the code, logs in output view and serial monitor are lost.
### To reproduce
- Disable auto-save from Settings > Auto Save
- Write some text in any file of the sketch
- OPTIONAL: to verify that this affects also output view and serial logs, perform any action that would write some logs in output and serial monitor
- On MacOS, enter sleep mode (Apple logo > Sleep)
- Reactivate the OS
The IDE reloads and changes to the file, output view and serial monitor are lost.
### Expected behavior
The IDE should maintain the current state when the OS enter sleep mode.
### Arduino IDE version
2.3.6
### Operating system
macOS
### Operating system version
15.3.2
### Additional context
Tested on 2.3.6, but the regression it's likely to be introduced in https://github.com/arduino/arduino-ide/pull/2654
Any tests for Windows and Linux is appreciated.
Related forum posts:
https://forum.arduino.cc/t/arduino-ide-2-3-6-arbitrarily-clears-the-output-and-serial-monitor/1371986
https://forum.arduino.cc/t/ide-2-3-5-problem/1371404
### Issue checklist
- [x] I searched for previous reports in [the issue tracker](https://github.com/arduino/arduino-ide/issues?q=)
- [x] I verified the problem still occurs when using the latest [nightly build](https://www.arduino.cc/en/software#nightly-builds)
- [x] My report contains all necessary details
Thank you for the info.
I subscribe it.