[Ovmsdev] NetManTask created twice
Stephen Casner
casner at acm.org
Tue Mar 20 14:34:52 HKT 2018
Mark,
I'm looking for the memory allocated to nonexistant tasks. In my code
I added a call to AddTaskToMap() after the creation of the NetManTask.
Now I see that the nonexistant task holding 264 bytes was an earlier
instance of NetManTask. Do you expect it to be created, killed, and
created again?
I'm considering making a public function that will query the task list
to populate the TaskMap, same as what is done now when the module
memory or module tasks command is invoked. Then I would add some
calls to that function at one or more places in system startup to try
to capture the other unnamed task while it exists. Any suggestions
for where to make such a call?
The output below is with the aforementioned AddTaskToMap() call added
plus some changes in ovms_module to list the tasks in module memory in
task number order so the order is consistent from one run to the next
and with the nonexistent ones first and marked with asterisk. I can
commit these changes if that is OK at this point.
-- Steve
Free 8-bit 31760/283148, 32-bit 27588/55864, SPIRAM 0/0
--Task-- Total DRAM D/IRAM IRAM SPIRAM +/- DRAM D/IRAM IRAM SPIRAM
no task * 5276 0 0 0 +5276 +0 +0 +0
main * 40076 0 0 0 +40076 +0 +0 +0
3FFE5CDC * 0 1396 0 0 +0 +1396 +0 +0
NetManTask * 0 264 0 0 +0 +264 +0 +0
esp_timer 55112 0 644 0 +55112 +0 +644 +0
eventTask 0 7620 0 0 +0 +7620 +0 +0
ipc0 10848 0 0 0 +10848 +0 +0 +0
ipc1 12 0 0 0 +12 +0 +0 +0
Tmr Svc 0 27808 0 0 +0 +27808 +0 +0
Housekeeping 17488 50384 0 0 +17488 +50384 +0 +0
tiT 128 1640 0 0 +128 +1640 +0 +0
AsyncConsole 0 20 27488 0 +0 +20 +27488 +0
mdns 0 112 0 0 +0 +112 +0 +0
wifi 0 1612 0 0 +0 +1612 +0 +0
NetManTask 4 2200 0 0 +4 +2200 +0 +0
More information about the OvmsDev
mailing list