Fork me on GitHub
#clojure-dev
<
2022-07-14
>
seancorfield00:07:06

We ran 1.12.0-alpha1 in our staging environment for a while didn't see any problems, so we rolled it up into production yesterday morning. Most of our apps have been performing just fine but one application was extremely unstable. There were a lot of changes in our build so it's taken me a while to run tests with intermediate builds to identify the commit that caused the instability -- and it appears to be the one that switched us from Clojure 1.11.1 to 1.12.0-alpha1. I've just deployed a new build of that app, built with Clojure 1.11.1 instead of 1.12.0-alpha1 as the only change from the main branch that we deployed yesterday and, so far, it is looking stable. It's very strange that only one out of over a dozen different applications seems to be affected, but it looks like some sort of memory leak as that application fairly quickly hits 100% heap usage with 1.12.0-alpha1 but is fine with 1.11.1 (and all our other apps seem fine with 1.12.0-alpha1).

Alex Miller (Clojure team)00:07:54

That seems deeply weird, would love to know more if you're able to take a heap dump and analyze

seancorfield00:07:37

Not going to be able to get to that for a few days I suspect. It's been a mad firefight since yesterday at 10 am to try to get that app stable and I still have a few fairly high priority issues to follow-up that should have gotten done since then.

seancorfield00:07:10

And, yes, deeply weird I agree.

seancorfield00:07:12

Luckily, we haven't already started using the new functions and the update to empty? 🙂

Alex Miller (Clojure team)01:07:10

No rush, I appreciate all your attention to our alphas

👍 2