Per Lundberg

@andrewl102 There was a clear plan suggested there so I tried bumping that PR a bit now.

@theigl Thanks. The problem for us is that 2.10 is such an old version (2014) that I'm not sure it would work for our use case.

@andrewl102 FWIW: I just tested your suggested workaround and it still runs into "unknown object tag -126" and similar errors sometimes, so it's unfortunately not a 100% safe fix. This...

I opened a separate issue and added a repro repository, moving the discussion to #274 since the workaround suggested in this issue does not work => separate root cause.

@RuedigerMoeller > Thanks for your extensive report, unfortunately i am very busy. Anyways as FST is used in our current software I will investigate as soon as possible (TM). Looking...

See #235, we discovered that issue and it seems to be our root cause.

@furti We have debugged our issue to great length and concluded that it seems to be related to our use of the G1GC garbage collector. Do you happen to be...

@furti Ok, maybe these are two different issues. For reference, my test repro is here https://github.com/perlun/fst-concurrency-issue - it would be interesting to see if this scenario fails for you _without...

@chrisco484 > Do you have String deduplication turned on as well as G1GC? At the moment, we use `-XX:+UseStringDeduplication` yes. I discussed this with @slovdahl and to the best of...

(For the moment, we are staying away from FST because of the severity of this bug. We cannot have the JVM crashing randomly; it's better to live with a few...