Skip to content

fix(esp_schedule): Using timestamp_cb pulled from NVS could cause crash#744

Merged
adokitkat merged 1 commit into
masterfrom
fix/esp_schedule_nvs_timestamp_cb_crash
May 7, 2026
Merged

fix(esp_schedule): Using timestamp_cb pulled from NVS could cause crash#744
adokitkat merged 1 commit into
masterfrom
fix/esp_schedule_nvs_timestamp_cb_crash

Conversation

@adokitkat
Copy link
Copy Markdown
Collaborator

Using timestamp_cb pulled from NVS could cause crash on reboot due to potential function address change during recompilation.

Closes #734

Checklist

  • CI passing

Change description

Added schedule->timestamp_cb = NULL; to esp_schedule_init funtion.

@adokitkat
Copy link
Copy Markdown
Collaborator Author

Hi @Junius00 , please take a look.

Copy link
Copy Markdown
Contributor

@Junius00 Junius00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, please bump the version patch number

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 7, 2026

Test Results

40 files  40 suites   1m 44s ⏱️
 6 tests  0 ✅  6 💤 0 ❌
13 runs   0 ✅ 13 💤 0 ❌

Results for commit 64c953e.

…sh on reboot due to potential function address change during recompilation

Closes #734
@adokitkat adokitkat force-pushed the fix/esp_schedule_nvs_timestamp_cb_crash branch from 64c953e to 4a19d11 Compare May 7, 2026 13:25
@adokitkat adokitkat enabled auto-merge May 7, 2026 13:26
@adokitkat adokitkat merged commit c958c15 into master May 7, 2026
47 of 48 checks passed
@mahavirj mahavirj deleted the fix/esp_schedule_nvs_timestamp_cb_crash branch May 12, 2026 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

timestamp_cb not nulled on NVS restore, causing crash on reboot after recompile (IEC-530)

3 participants