[Ovmsdev] Frequent Crashes

[Michael Balzer]

By reducing my Wifi router signal strength and lowering the wifi sq
configs I managed to put my module additionally under networking stress,
with multiple network changes in/out Wifi.

Sadly, still no issue turning up…

So, if you can reproduce the exact circumstances in your setting and
narrow down the cause, that could be very helpful.

Regards,
Michael


Am 12.08.20 um 13:10 schrieb Michael Balzer:
> The script has now been running on my ticker.1 for nearly 4 hours
> without any issues.
>
> Some other reports included a poor Wifi signal. Does that apply to
> your situation as well? I can't easily reproduce that on my bench.
>
> Regards,
> Michael
>
>
> Am 12.08.20 um 09:18 schrieb Michael Balzer:
>> Derek,
>>
>> what do you mean by "match the crash timings"? Did you see the crash
>> happen at the GC run? If you checked your file log, be aware the log
>> may be cut off by the crash. The WDT reboot isn't polite to our
>> logging task or unflushed file buffers.
>>
>> If there's a bug in the DukTape GC, that could well block further JS
>> processing and thus trigger the WDT. The last GC bugs fixed in
>> DukTape have been in release 2.1.0 (2017-04-15):
>> https://duktape.org/download.html
>>
>> Your test script doesn't allocate much memory, and as it was bound to
>> the system.wifi.sta.disconnected event should have run at most 6
>> times per minute -- not much stress for the GC… I'll bind your test
>> script to ticker.1 on my bench module.
>>
>> Regards,
>> Michael
>>
>>
>> Am 12.08.20 um 08:52 schrieb Derek Caudwell:
>>> Hi Michael,
>>>
>>> The following is the content of my "dummy" script, so it shouldn't
>>> cause any looping issues:
>>>  var history = {
>>>   "test": [],
>>>   "v.p.odometer": [],
>>>   "v.p.altitude": [],
>>>   "v.b.energy.used": [],
>>>   "v.b.energy.recd": [],
>>> };
>>> var lastOdo = 0;
>>> var saveOdo = 0;
>>>
>>> print(Duktape.enc('jc', history));
>>>
>>> I deleted the script and folder before seeing your suggestion on
>>> task priority, but I could reinstate and try at some point.
>>>
>>> Since deleting the script and the events folder the module has been
>>> stable for over 10 hours. I see there is garbage collection every
>>> 60s which seems to match the crash timings to within a second or so,
>>> could this be the cause??
>>>
>>> Kind regards
>>> Derek
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>
>> -- 
>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
> -- 
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200812/7d16de88/attachment.htm>