8000 Correction on Heap API available from ISR by mhightower83 · Pull Request #8708 · esp8266/Arduino · GitHub
[go: up one dir, main page]
Skip to content

Correction on Heap API available from ISR #8708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 4, 2022
Merged

Correction on Heap API available from ISR #8708

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
97ab74e
Correction on Heap API available from ISR
mhightower83 Nov 3, 2022
d4da074
Expand reason for avoid realloc/free
mhightower83 Nov 4, 2022
142deb8
Merge branch 'master' into pr-doc-correction
mcspr Nov 4, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Expand reason for avoid realloc/free
  • Loading branch information
@mhightower83
mhightower83 committed Nov 4, 2022
commit d4da074bc3cf76b19071eeda568b4ef50488a1e8
4 changes: 4 additions & 0 deletions doc/reference.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,10 @@ and have several limitations:
that ``String``, ``std::string``, ``std::vector`` and other classes which
use contiguous memory that may be resized must be used with extreme care
(ensuring strings aren't changed, vector elements aren't added, etc.).
The underlying problem, an allocation address could be actively in use at
the instant of an interrupt. Upon return, the address actively in use may
be invalid after an ISR uses ``realloc`` or ``free`` against the same
allocation.

* The C++ ``new`` and ``delete`` operators must NEVER be used in an ISR. Their
call path is not in IRAM. Using any routines or objects that use the ``new``
Expand Down
0