-
Notifications
You must be signed in to change notification settings - Fork 131
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
HTTPS | ESP32 | Core 0 panic'ed #85
Comments
I cannot reproduce your error by myself, but there seems to be an issue with the state machine of the connection handler. Just removing that line might solve the issue but it leads to resources not being freed correctly, which might catch you at some later point in time. I'll have a look at it. What would really help me is if you could feed the backtrace ...
... into the ESP stacktrace decoder. If you're not using the Arduino IDE (but have it at least installed), you can call the stacktrace decoder for CLI: java -jar EspStackTraceDecoder.jar /your/arduino/folder/hardware/espressif/esp32/tools/xtensa-esp32-elf/bin/xtensa-esp32-elf-addr2line /path/to/application.elf /file/with/backtrace.txt For Platform IO, you'd find the .elf file in the .pio subdirectory in your project. |
Hi,
This error is well reproducabe with unstable Wifi connection as it is connected to session disconnections or other similar problems coming from SSL. I created a pull request with the modification I'm using: #89 |
I have been having the same problem with exceptions, especially related to poor signal quality. I'm only using HTTP, but what I have tried instead of commenting out the closeConnection() call is to set a flag and do the closeConnection in the loop() code instead, based on that flag being set. My test has been connecting to the ESP's AP, then back to home WiFi from a mobile. I note that updateBuffer() is called from numerous places, and this may well be the underlying problem given the async nature of some calls..... In updateBuffer():
in loop():
|
Because of closeConnection() the SSL context is released. Flow:
The following methods should check for a valid SSL context, before calling a SSL function:
With the added check, there is no reset anymore. |
@fhessel just came across that too. |
Hello
I have a problem with the library on the ESP32 platform. The situation is as follows:
- the browser makes a connection on 2-3 sockets (this is its nature and we will not change it :))
I present the exact outline of the situation in the logs.
First of all - I added a few logs (CLOSING n) in the HTTPSConnection.cpp file in the closeConnection () method to better explain the situation :
The result is this debug:
So my question is, did anyone else have such a problem?
To avoid this error, I have temporarily removed the line shown in the screenshot below. Will this solution not affect the library's operation?
File
HTTPConnection.cpp -> int HTTPConnection::updateBuffer()
After commenting on this line, the problem does not occur.
Thank you in advance for your help.
Greetings
The text was updated successfully, but these errors were encountered: