[GH-ISSUE #416] handleWifiSave() headless issue #348

New issue

Closed

opened 2026-02-28 01:24:53 +03:00 by kerem · 4 comments

kerem commented

2026-02-28 01:24:53 +03:00

Owner

Originally created by @suculent on GitHub (Sep 8, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/416

Hello, I'm receiving this weird issue on AutoConnect. It should be in STA mode but it switches to softAP and crashes.

Source (line 195):
github.com/suculent/thinx-lib-esp8266-arduinoc@9d598cc119/src/THiNXLib.cpp

What is my concern that the handleWifiSave() method which:

a) seems to send WiFi save page while there is no user connected at all in the station mode...
b) does not server->close(); the connection (may not be such an issue)

Log:

*WM:
*WM: AutoConnect
bcn 0
del if1
mode : sta(5c:cf:7f:f0:94:9a)
mode : sta(5c:cf:7f:f0:94:9a) + softAP(5e:cf:7f:f0:94:9a)
Fatal exception 28(LoadProhibitedCause)

Stacktrace:

0x4020125a: Print::write(char const*) at ??:?
0x4020125a: Print::write(char const*) at ??:?
0x40107530: vPortFree at ??:?
0x40216f0c: wifi_set_broadcast_if at ??:?
0x40216f42: wifi_set_opmode at ??:?
0x40201344: Print::print(char const*) at ??:?
0x402033ef: ESP8266WiFiGenericClass::mode(WiFiMode) at ??:?
0x4020e343: WiFiManager::handleWifiSave() at ??:?
0x4020fba0: ESP8266HTTPUpdate::runUpdate(Stream&, unsigned int, String, int) at ??:?
0x4010020c: _umm_free at umm_malloc.c:?
0x40100688: free at ??:?
0x4024ef9f: chip_v6_unset_chanfreq at ??:?
0x4020fd15: ESP8266HTTPUpdate::handleUpdate(HTTPClient&, String const&, bool) at ??:?
0x40202f96: uart_wait_tx_empty at ??:?
0x40217b8b: wifi_station_get_connect_status at ??:?
0x402037cc: ESP8266WiFiSTAClass::status() at ??:?
0x4020483c: THiNX::connect_wifi() at ??:?
0x40204928: THiNX::connect() at ??:?
0x40204962: THiNX::connect() at ??:?
0x40214298: String::StringIfHelper() const at ??:?
0x4020175d: String::copy(char const*, unsigned int) at ??:?
0x402037cc: ESP8266WiFiSTAClass::status() at ??:?
0x4020661d: THiNX::loop() at ??:?
0x40201261: Print::write(char const*) at ??:?
0x4010020c: _umm_free at umm_malloc.c:?
0x40100688: free at ??:?
0x40214ad5: loop at ??:?

Originally created by @suculent on GitHub (Sep 8, 2017). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/416 Hello, I'm receiving this weird issue on AutoConnect. It should be in STA mode but it switches to softAP and crashes. Source (line 195): https://github.com/suculent/thinx-lib-esp8266-arduinoc/blob/9d598cc119d78f39398f15acd14c3d822c95df77/src/THiNXLib.cpp What is my concern that the handleWifiSave() method which: a) seems to send WiFi save page while there is no user connected at all in the station mode... b) does not server->close(); the connection (may not be such an issue) Log: ``` *WM: *WM: AutoConnect bcn 0 del if1 mode : sta(5c:cf:7f:f0:94:9a) mode : sta(5c:cf:7f:f0:94:9a) + softAP(5e:cf:7f:f0:94:9a) Fatal exception 28(LoadProhibitedCause) ``` Stacktrace: ``` 0x4020125a: Print::write(char const*) at ??:? 0x4020125a: Print::write(char const*) at ??:? 0x40107530: vPortFree at ??:? 0x40216f0c: wifi_set_broadcast_if at ??:? 0x40216f42: wifi_set_opmode at ??:? 0x40201344: Print::print(char const*) at ??:? 0x402033ef: ESP8266WiFiGenericClass::mode(WiFiMode) at ??:? 0x4020e343: WiFiManager::handleWifiSave() at ??:? 0x4020fba0: ESP8266HTTPUpdate::runUpdate(Stream&, unsigned int, String, int) at ??:? 0x4010020c: _umm_free at umm_malloc.c:? 0x40100688: free at ??:? 0x4024ef9f: chip_v6_unset_chanfreq at ??:? 0x4020fd15: ESP8266HTTPUpdate::handleUpdate(HTTPClient&, String const&, bool) at ??:? 0x40202f96: uart_wait_tx_empty at ??:? 0x40217b8b: wifi_station_get_connect_status at ??:? 0x402037cc: ESP8266WiFiSTAClass::status() at ??:? 0x4020483c: THiNX::connect_wifi() at ??:? 0x40204928: THiNX::connect() at ??:? 0x40204962: THiNX::connect() at ??:? 0x40214298: String::StringIfHelper() const at ??:? 0x4020175d: String::copy(char const*, unsigned int) at ??:? 0x402037cc: ESP8266WiFiSTAClass::status() at ??:? 0x4020661d: THiNX::loop() at ??:? 0x40201261: Print::write(char const*) at ??:? 0x4010020c: _umm_free at umm_malloc.c:? 0x40100688: free at ??:? 0x40214ad5: loop at ??:? ```

kerem closed this issue

2026-02-28 01:24:53 +03:00

kerem commented

2026-02-28 01:24:53 +03:00

Author

Owner

@suculent commented on GitHub (Sep 8, 2017):

I don't understand why this happens, when handleWifiSave is callback set only here:

server->on("/wifisave", std::bind(&WiFiManager::handleWifiSave, this));

@suculent commented on GitHub (Sep 8, 2017): I don't understand why this happens, when handleWifiSave is callback set only here: ``` server->on("/wifisave", std::bind(&WiFiManager::handleWifiSave, this)); ```

kerem commented

2026-02-28 01:24:53 +03:00

Author

Owner

@tablatronix commented on GitHub (Sep 8, 2017):

That is alot of stuff going on, that exception is typically an illegal memory access problem. You are gonna have to come up with a test case

@tablatronix commented on GitHub (Sep 8, 2017): That is alot of stuff going on, that exception is typically an illegal memory access problem. You are gonna have to come up with a test case

kerem commented

2026-02-28 01:24:53 +03:00

Author

Owner

@suculent commented on GitHub (Sep 8, 2017):

Should I use ArduinoUnit? I’m thinking about unit tests for my library as it becomes huge.

Question is, how could the handleWifiSave() happen at the first place. No captive portal client should be redirected to this without doing anything meaningful.

On 8 Sep 2017, at 20:10, Shawn A notifications@github.com wrote:

That is alot of stuff going on, that exception is typically an illegal memory access problem. You are gonna have to come up with a test case

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tzapu/WiFiManager/issues/416#issuecomment-328175624, or mute the thread https://github.com/notifications/unsubscribe-auth/AANix_Ak53WhT1G6wdAmJELlugF7hUdSks5sgYMegaJpZM4PRccE.

@suculent commented on GitHub (Sep 8, 2017): Should I use ArduinoUnit? I’m thinking about unit tests for my library as it becomes huge. Question is, how could the handleWifiSave() happen at the first place. No captive portal client should be redirected to this without doing anything meaningful. > On 8 Sep 2017, at 20:10, Shawn A <notifications@github.com> wrote: > > That is alot of stuff going on, that exception is typically an illegal memory access problem. You are gonna have to come up with a test case > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub <https://github.com/tzapu/WiFiManager/issues/416#issuecomment-328175624>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANix_Ak53WhT1G6wdAmJELlugF7hUdSks5sgYMegaJpZM4PRccE>. >

kerem commented

2026-02-28 01:24:53 +03:00

Author

Owner

@tablatronix commented on GitHub (Oct 29, 2017):

I mean a minimal code to reproduce

@tablatronix commented on GitHub (Oct 29, 2017): I mean a minimal code to reproduce