[Ovmsdev] Branch for-v3.3 network issues

[Craig Leres]

On 9/17/21 12:24 AM, Michael Balzer wrote:
> 
> I've been running the new for-v3.3 version this week on both of my 
> modules without ppp issues.
> 
> Duktape still occasionally runs into the null/undefined issue with for…in:
> 
> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/474#issuecomment-744005044
> 
> for…in normally doesn't throw an error even if you run over null or 
> undefined.
> 
> I think both could still be the SPIRAM bug, now probably only occurring 
> with very specific conditions. We build with LWIP using SPIRAM as well, 
> so the PPP instance is allocated from SPIRAM also. Reallocating the 
> instance on each new connect implies a higher chance of triggering the 
> problem if it's address specific. The Duktape stack object addresses 
> vary continuously with the running event handlers and user interactions, 
> so that also has a high chance of occasionally triggering an address 
> specific bug.
> 
> We need to test the revision 3 ESP32 on this.

What can I do to test this on my frankenstein v3 module?

		Craig