Adding an element to MutableIntSet causes it to be unable to find another item in the set [352560465]

Fixed

Bug

Status Update

No update yet.

Description

an...@google.com

created issue #1

Jul 11, 2024 06:07PM

I'm seeing unexpected behavior after adding an item to a heavily used MutableIntSet. In the following code snippet, 24 is previously added to a MutableSet. After adding another value, 24 in set then returns false.

val set = MutableIntSet()
...

assertTrue(24 in set) // true
set += 6
assertTrue(24 in set) // false

I've attached a deterministic (but not at all concise) repro case to this issue. The ... in the above snippet is actually a sequence of 2,442 specific additions and removals that cause this behavior. I'm sure there's a more concise repro case, this is just one that I immediately have at hand.

This is starting in my local copy of a CL after a recent rebase onto androidx-main, so I'm guessing aosp/3165182 is the culprit.

intSetCorruptionReproTest.kt

33 KB

Download

Comments

ro...@google.com <ro...@google.com> #2Jul 11, 2024 07:12PM

Accepted by ro...@google.com.

The CL is merged. This option will be available in the next canary release.

ro...@google.com <ro...@google.com> #3Jul 11, 2024 07:32PM

Which version? I don't see an option in 33.1.2

an...@google.com <an...@google.com> #4Jul 11, 2024 10:35PM

It's gonna be available since 33.1.4. The CL is merged after the build 9654821 which is 33.1.3.

ro...@google.com <ro...@google.com> #5Jul 11, 2024 11:36PM

Thanks!

ap...@google.com <ap...@google.com> #6Jul 12, 2024 07:37PM

Marked as fixed.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Emulator 33.1.4

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

ap...@google.com <ap...@google.com> #7Aug 5, 2024 05:18PM

Thnx

pr...@google.com <pr...@google.com> #8Aug 13, 2024 06:58PM

Gracias

pr...@google.com <pr...@google.com> #9Sep 5, 2024 08:09PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.collection:collection:1.5.0-alpha01
androidx.collection:collection-iosarm64:1.5.0-alpha01
androidx.collection:collection-iossimulatorarm64:1.5.0-alpha01
androidx.collection:collection-iosx64:1.5.0-alpha01
androidx.collection:collection-jvm:1.5.0-alpha01
androidx.collection:collection-linuxarm64:1.5.0-alpha01
androidx.collection:collection-linuxx64:1.5.0-alpha01
androidx.collection:collection-macosarm64:1.5.0-alpha01
androidx.collection:collection-macosx64:1.5.0-alpha01
androidx.collection:collection-tvosarm64:1.5.0-alpha01
androidx.collection:collection-tvossimulatorarm64:1.5.0-alpha01
androidx.collection:collection-tvosx64:1.5.0-alpha01
androidx.collection:collection-watchosarm32:1.5.0-alpha01
androidx.collection:collection-watchosarm64:1.5.0-alpha01
androidx.collection:collection-watchossimulatorarm64:1.5.0-alpha01
androidx.collection:collection-watchosx64:1.5.0-alpha01