Modifying profiles.json causes multiple settings reloads #1167

Closed
opened 2026-01-30 22:17:58 +00:00 by claunia · 3 comments
Owner

Originally created by @d-bingham on GitHub (May 16, 2019).

Originally assigned to: @zadjii-msft on GitHub.

This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: Microsoft Windows [Version 10.0.18362.86]

  • What you're doing and what's happening: When editing profiles.json, saving a modified version of the file generates multiple app-wide settings refreshes.

  • What's wrong / what should be happening instead: Modifying the settings file should only generate one app-wide settings update

Originally created by @d-bingham on GitHub (May 16, 2019). Originally assigned to: @zadjii-msft on GitHub. This bug-tracker is monitored by Windows Console development team and other technical types. **We like detail!** If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). > **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: Microsoft Windows [Version 10.0.18362.86] * What you're doing and what's happening: When editing profiles.json, saving a _modified_ version of the file generates multiple app-wide settings refreshes. * What's wrong / what should be happening instead: Modifying the settings file should only generate one app-wide settings update
claunia added the Resolution-Fix-CommittedArea-SettingsIssue-BugProduct-Terminal labels 2026-01-30 22:17:58 +00:00
Author
Owner

@fearthecowboy commented on GitHub (May 16, 2019):

It looks like in TerminalApp::CascadiaSettings it has

  static std::unique_ptr<CascadiaSettings> LoadAll(const bool saveOnLoad = true);

saveOnLoad is true and it's only ever called with the default value.

I'd think that this should not save by default - if it loaded, it should be fine to load later, there's little gained by saving it (which also reformats the json. GRRRRR 😠 ).

@fearthecowboy commented on GitHub (May 16, 2019): It looks like in `TerminalApp::CascadiaSettings` it has ``` c++ static std::unique_ptr<CascadiaSettings> LoadAll(const bool saveOnLoad = true); ``` `saveOnLoad` is `true` and it's only ever called with the default value. I'd think that this should not save by default - if it loaded, it should be fine to load later, there's little gained by saving it (which also reformats the json. GRRRRR 😠 ).
Author
Owner

@zadjii-msft commented on GitHub (May 16, 2019):

Yea I think I actually have a fix for this in #748 here

@zadjii-msft commented on GitHub (May 16, 2019): Yea I think I actually have a fix for this in #748 [here](https://github.com/microsoft/terminal/pull/748/files#diff-a011f61f234a66ac8dd94efe8e488244R408)
Author
Owner

@d-bingham commented on GitHub (May 16, 2019):

Yeah, the fix in #748 fixes the problem.

@d-bingham commented on GitHub (May 16, 2019): Yeah, the fix in #748 fixes the problem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1167