Skip to content
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.

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

Odd stack watermark for server task #105

Open
Barabas5532 opened this issue Dec 22, 2023 · 0 comments
Open

Odd stack watermark for server task #105

Barabas5532 opened this issue Dec 22, 2023 · 0 comments
Labels
P1 Nice to have features

Comments

@Barabas5532
Copy link
Member

The server task stack usage immediately at statup seems to depend on the ApiMessage size.

Printing the stack watermark at this spot:

ESP_LOGI(TAG, "Got websocket upgrade request");

reports different values depening on the size of the API message struct. This doesn't make sense, as at this point in the execution, the server has not interacted with any API messages yet. It has pointers to the input and output queues, which do not depend on the size of the message.

This function also decodes the messages later on, maybe the stack for those calls gets allocated on entry to the function?

Sprinkle some more watermark prints to work out what is going on.

@Barabas5532 Barabas5532 added the P1 Nice to have features label Dec 22, 2023
@Barabas5532 Barabas5532 moved this to Implementation in progress in ShrapnelDSP Dec 22, 2023
@Barabas5532 Barabas5532 moved this from Implementation in progress to Specification in progress in ShrapnelDSP Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Nice to have features
Projects
Status: Specification in progress
Development

No branches or pull requests

1 participant