@mister @mstanley Anecdotally, I can report the 1.3.1 memory leak fix almost certainly solved the eventual-infinite-never-reconnect-green-flash-ad-infinitum issue that was the root of this thread, and which was the source of my troubles above, and which is different from the never-connects issue.
I have a 1.3.1 Boron in the field where there is highly variable signal where Borons used to always infinitely drop the connection. How long they went before dropping varied between a few hours and two months, but they ALWAYS invariably entered a never-reconnect infinite-green-flashing state.
Now, with 1.3.1, my Boron faithfully reconnects during the semi-regular bouts of time where cell service vanishes at this spot. Currently my Boron is at 23 disconnects, uploading rock-solid for days. Cell service went out for like a 36 hour period last week, and it faithfully reconnected.
Insofar as this thread is concerned, i.e. regarding that particular issue, I am very, VERY satisfied to say that the issue appears to be resolved (knock on wood), and I can resume using Particle Boron.
The only source of nervousness is how a true memory leak can be solved by making some task a higher priority in the operating system. That sounds like a band-aid, and not an actual solution to a memory leak, to me. But I trust the engineers fixed the issue and there will be NO permanently disabling memory leak no matter how long a disconnection state lasts and no matter how many disconnnects come. @mstanley, do you agree with that?