mem::uninitialized/zeroed regressions

• accepted-0.3.2 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• address-formatter-0.2.1 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• apply-user-defaults-0.1.2 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• arc-cache-0.2.4 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• arc_ast-0.1.0 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• arc_from_yaml-0.1.0 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• arendur-0.0.5 test passed test failed
  UB reported

• aristeia-0.2.3 test passed test failed
  Likely spurious; crate does not use uninitialized and test name cotnains "random"

• async-local-bounded-channel-0.1.0 test passed test failed
  UB in generic-array, fixed upstream but semver-incompatible; regressed crate has no issue tracker

• atomicring-1.2.4 test passed test failed
  Likely spurious; test cases uses global variable (so concurrently running tests interfere)

• autoperf-0.9.4 test passed build failed
  Spurious: "SIGSEGV: invalid memory reference" during build

• balena-cdsl-0.10.6 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• bar-config-0.2.1 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• basic_dsp_matrix-0.8.0 test passed test failed
  UB reported; on master the panic is fixed but the UB is not

• basin2-lib-152.1.0 test passed test failed
  Cannot find repository, but error indicates linked_hash_map.

• batch-loader-0.1.0 test passed test failed
  Seeminlgly unmaintained; ancient version of crossbeam where many soundness bugs have been fixed

• belay-0.5.0 test passed test failed
  UB in linked_hashmap, sent PR to yaml-rust which this crate depends on

• bip_disk-0.6.0 test passed test failed
  UB in an old version of corssbeam's queue

• bip_metainfo-0.12.0 test passed test failed
  Likely UB in ancient crossbeam

• bip_peer-0.5.0 test passed test failed
  Likely UB in ancient crossbeam

• bitjo-0.1.1 test passed test failed
  UB in linked_hash_map which is used by serde_yaml. Sent a pr to serde_yaml. (pr to this crate is pending)

• bson-0.14.1 test passed test failed
  UB in linked_hash_map. Opened pull request in upstream of bson fork

• cache_2q-0.10.0 test passed test failed
  UB in linked_hashmap. Opened pull request

• caelum-vcdm-0.2.0 test passed test failed
  UB in linked_hashmap. Opened pull request merge request

• carboxyl_time-0.0.3 test passed test failed - a different regression , not sure if related (will investigate)
  Ralf: looks spurious to me, error "delta > Duration::microseconds(9500)" indicates something timing-dependent.

• cargo-bump-1.1.0 test passed test failed
  UB in linked_hashmap which is used by toml_edit (covered below)

• cargo-crate-type-0.1.0 test passed test failed
  UB in linked_hashmap which is used by toml_edit (covered below)

• cargo-flash-0.6.0 test passed build failed
  Caused due to linked_hash_map via probe-rs

• cargo-toml-builder-0.3.0 test passed test failed
  UB in linked_hash_map via toml_edit

• casbin-0.6.0 test passed test failed
  UB in linked_hash_map via ttl_cache, pr opened in ttl (which was closed eh)

• casperlabs-engine-core-0.5.1 test passed test failed
  UB in linked_hashmap, opened pr

• cb-stm-temp-0.3.0 test passed test failed
  UB in old (unsupported) version of crossbeam-epoch (0.4.3) which depends on broken memoffset 0.2

• chess-3.1.1 test passed test failed
  UB in code, fixed in latest version

• cobalt-0.22.0 test passed test failed
  unrelated failure (looks like timing)

• conduit-hyper-0.3.0-alpha.2 test passed test failed
  unrelated (looks like timing)

• config-spirit-fork-0.1.0 test passed test failed - linked_hash_map in yaml_rust

• config-0.10.1 test passed test failed
  UB in linked_hash_map via yaml_rust

• cord-broker-0.1.0 test passed test failed
  UB in tokio-sync (i think), dependency.
  Fixed in tokio; crates needs to update to tokio 0.2. Crate author informed.

• cosmwasm-vm-0.7.2 test passed test failed
  UB in LRU that has been fixed upstream; author informed.

• crack-0.1.0 test passed test failed
  UB in old version of crossbeam

• crev-data-0.16.0 test passed test failed
  UB in linked_hashmap through serde_yaml

• crev-lib-0.16.0 test passed test failed
  UB in linked_hashmap through serde_yaml

• crossbeam-arccell-0.6.4 test passed test failed
  Crate is yanked

• crossbeam-stm-0.6.1 test passed test failed
  Crate is yanked

• ddh-0.10.9 test passed test failed
  could not trace it but created an issue
  UB in crossbeam-epoch-0.7.1 (depends on broken memoffset 0.2)

• decimal-2.0.4 test passed test failed
  UB in code (initialized function being usedion being used). Opened issue

• device-types-0.1.4 test passed test failed
  can't find crate on github. UB is from sized-chinks where it has been fixed, but the crate (indirectly?) depends on an ancient version.

• dotcopter-0.4.5 test passed test failed
  UB in linked_hash_map via yaml_rust

• doublecross-0.2.1 test passed test failed
  UB in old version of crossbeam. Code is fixed in crossbeam 0.4

• dtool-0.9.0 test passed test failed
  UB in linked_hashmap. PR opened

• dynfmt-0.1.2 test passed test failed
  UB in code, has been fixed already, release pending

• ejdb-0.4.0 test passed test failed
  UB in linked_hash_map

• ergo_sync-0.1.0 test passed test failed
  UB in old version of crossbeam

• esl-0.3.1 test passed test failed
  UB in linked_hash_map via serde_yaml

• evaltrees-0.1.0 test passed test failed
  memory error, likely double-panic after UB in linked-hash-map

• exclave-0.2.6 test passed test failed
  Unclear; no repository linked in crates.io

• favocon-1.1.0 test passed test failed
  old crossbeam-epoch

• fdup-2.0.2 test passed test failed
  old crossbeam-epoch

• frugalos_core-0.1.1 test passed test failed
  UB in linked_hash_map via serde_yaml

• gary-core-0.0.1 test passed test failed
  UB in linked_hash_map via serde_yaml

• gatekeeper-0.1.0 test passed test failed
  UB in linked_hash_map via serde_yaml

• gdb-server-0.6.0 test passed build failed
  UB in linked_hash_map via probe_rs

• gimei-0.1.1 test passed test failed
  likely UB in linked_hash_map via yaml_rust

• git-req-2.2.0 test passed build failed
  UB in linked_hash_map via yaml_rust

• hammersbald-2.4.0 test passed test failed
  UB in linked_hash_map via lru_cache

• hassium-core-0.1.3 test passed test failed
  Double-panic, cause unclear. Cannot access code.

• hellcheck-0.1.2 test passed test failed
  UB in linked_hash_map via serde_yaml

• hrx-0.1.0 test passed test failed
  UB in linked_hashmap. created a pr

• id3-image-0.1.2 test passed test failed
  old crossbeam-epoch pinned in lockfile; author notified

• indextree-ng-1.0.5 test passed test failed
  The code on GH doesn't match the filenames in the crater log, no idea what happens there. But it probably does not matter; this looks like a dead fork of indextree and the original is fine.

• intarray-0.1.0 test passed test failed
  UB in linked_hash_map via serde_yaml

• intrusive_splay_tree-0.1.0 test passed test failed
  UB in code. Issue opened

• intspan-0.4.12 test passed test failed
  UB in linked_hash_map via serde_yaml

• ipc-orchestrator-0.3.3 test passed test failed
  looks spurious

• itchy-0.2.1 test passed test failed
  UB in decimal, covered above

• json_typegen-0.4.0 test passed test failed
  UB in json_typgen_shared. covered below

• json_typegen_shared-0.4.0 test passed test failed
  UB in linked_hash_map. PR opened

• know-thy-shell-0.1.12 test passed build failed
  crossbeam-epoch 0.7.1 is broken; fixed in 0.7.2. Cannot find code for this crate.

• krakend_conf-0.1.0 test passed test failed
  UB in linked_hash_map via serde_yaml

• ktmpl-0.9.0 test passed test failed
  UB in linked_hash_map via serde_yaml

• kube-conf-0.2.0 test passed test failed
  UB in linked_hash_map via serde_yaml

• lib3h_zombie_actor-0.0.42 test passed test failed
  Looks like a concurrency test, probably spurious.

• libnetkeeper-0.1.0 test passed test failed
  UB in linked_hash_map, Opened issue

• libpasta-0.1.0 test passed test failed
  UB in linked_hash_map via serde_yaml

• link-0.1.0 test passed test failed
  experimental code, author will fix it

• linked-hash-map-0.5.2 test passed test failed
  UB in code, fixed in 0.5.3, causes regressions in many crates

• linked_hash_set-0.1.3 test passed test failed
  depends on linked-hash-map

• littlefs-0.2.0 test passed test failed
  UB in code, created issue

• localnative_core-0.3.7 test passed test failed
  UB in linked_hashmap via linked_hash_set
  PR opened.

• lockfreehashmap-0.1.2 test passed test failed
  looks like the crossbeam-epoch UB, author notified

• log4rs-routing-appender-0.4.0 test passed test failed
  UB in linked_hash_map. Created pr

• lru-cache-0.1.2 test passed test failed
  UB in linked_hash_map

• lru-disk-cache-0.4.0 test passed test failed
  UB in linked_hash_map

• madato-0.5.3 test passed test failed
  UB in linked_hash_map

• magnet_schema-0.8.0 test passed test failed
  UB in linked_hash_map dependency in bson

• marked-yaml-0.1.0 test passed test failed
  UB in linked_hash_map

• mdl-1.0.4 test passed test failed
  seems unrelated; lots of concurrency so likely a scheduler thing

• median-0.3.1 test passed test failed
  Another instance of this generic_array bug

• mediawiki_parser-0.4.2 test passed build failed
  UB in linked_hash_map via serde_yaml

• memoization-0.1.0 test passed test failed
  UB in crate, author notified

• merge-yaml-hash-0.2.0 test passed test failed
  UB in linked-hash-map

• merger-0.1.0 test passed test failed
  UB in linked-hash-map

• mime-detective-1.0.0 test passed test failed
  SIGBUS? likely spurious

• minecraft-protocol-0.1.0 test passed test failed
  UB in linked-hash-map

• mkbookpdf-1.1.0 test passed test failed
  UB in linked-hash-map

• mozangle-0.3.1 test passed test failed
  UB in crate, author notified.

• mozjpeg-sys-0.10.4 test passed build failed
  old crossbeam-epoch; not sure through which transitive dependency but the crate has updated its deps since then

• multicache-0.6.1 test passed test failed
  UB in linked-hash-map

• multistream-batch-0.1.2 test passed test failed
  UB in linked-hash-map

• my-iot-0.41.0 test passed test failed
  UB in linked-hash-map

• myelin-engine-0.14.1 test passed test failed
  Depends on old version of nalgebra, newer versions don't panic (they are still UB though…)

• named-binary-tag-0.2.3 test passed test failed
  UB in linked-hash-map

• nerd_fonts-0.1.9 test passed test failed
  UB in linked-hash-map

• nickel_cors-0.3.3 test passed test failed
  Looks unrelated (some HTTP headers changed?)

• nom-psl-1.2.0 test passed test failed
  UB in linked-hash-map

• nonogrid-0.6.2 test passed test failed
  UB in LRU that has been fixed upstream; newer nonogrid depends on newer lru

• nonvolatile-0.7.0 test passed test failed
  UB in linked-hash-map

• npnc-0.2.1 test passed test failed
  Crate uses mem::uninitialized incorrectly; author notified

• odin-0.1.0 test passed test failed
  UB in linked-hash-map

• openapiv3-0.3.0 test passed test failed
  UB in linked-hash-map

• over-there-utils-0.1.0-alpha.1 test passed test failed
  Sounds like a timing issue

• oxygengine-animation-0.7.2 test passed build failed
  UB in linked-hash-map

• oxygengine-audio-backend-web-0.7.2 test passed build failed
  UB in linked-hash-map. I will assume all the other "oxygenengine-*" crates also have the same problem.

• oxygengine-audio-0.7.2 test passed build failed

• oxygengine-backend-web-0.7.2 test passed build failed

• oxygengine-composite-renderer-backend-web-0.7.2 test passed build failed

• oxygengine-composite-renderer-0.7.2 test passed build failed

• oxygengine-ignite-derive-0.7.2 test passed build failed

• oxygengine-input-device-web-0.7.2 test passed build failed

• oxygengine-input-0.7.2 test passed build failed

• oxygengine-integration-p2d-cr-0.7.2 test passed build failed

• oxygengine-integration-vn-cr-0.7.2 test passed build failed

• oxygengine-navigation-0.7.2 test passed build failed

• oxygengine-network-backend-desktop-0.7.2 test passed build failed

• oxygengine-network-backend-native-0.7.2 test passed build failed

• oxygengine-network-backend-web-0.7.2 test passed build failed

• oxygengine-network-0.7.2 test passed build failed

• oxygengine-physics-2d-0.7.2 test passed build failed

• oxygengine-script-flow-0.7.2 test passed build failed

• oxygengine-script-web-0.7.2 test passed build failed

• oxygengine-visual-novel-0.7.2 test passed build failed

• oxygengine-0.7.2 test passed build failed

• phonenumber-0.2.4+8.11.3 test passed test failed
  Not sure what is happening… a regex cache mutex gets poisoned? Probably caused by regex-cache depending on linked_hash_map.

• pq-1.4.0 test passed test failed
  UB in linked-hash-map

• probe-rs-cli-0.6.1 test passed build failed
  UB in linked_hash_map

• probe-rs-0.6.1 test passed build failed
  UB in linked_hash_map

• pure_decimal-0.0.7 test passed test failed
  UB in decimal crate (see above)

• purezen-0.0.2 test passed test failed
  UB in generic-array, fixed upstream but semver-incompatible

• quad-image-0.1.1 test passed test failed
  UB in crossbeam-epoch 0.7.1 (needs 0.7.2); crate lockfile has been updated since then

• quickcfg-0.4.0 test passed test failed
  UB in linked_hash_map

• rangemap-0.1.4 test passed test failed
  Strange build failure: "found possibly newer version of crate time which chrono depends on"

• rdedup-lib-3.1.0 test passed test failed
  UB in linked_hash_map

• regex-cache-0.2.0 test passed test failed
  UB in linked_hash_map

• replicante_util_actixweb-0.1.0 test passed test failed
  UB in old sized-chunks; since then 0.2.0 was released with its dependencies updated.

• replicante_util_tracing-0.3.2 test passed test failed
  UB in linked_hash_map

• reproto-derive-0.3.36 test passed test failed
  UB in linked_hash_map

• rhusics-ecs-0.7.0 test passed test failed
  UB in crate, but fixed in master.asked for new release.

• roadmap-0.2.0 test passed test failed
  UB in linked_hash_map

• rqrr-0.2.0 test passed test failed
  UB in LRU that has been fixed upstream; author notified

• rtps-elements-0.2.0 test passed build failed
  UB in linked_hash_map

• rtps-gen-0.2.0 test passed build failed
  UB in linked_hash_map

• rusqlite-0.22.0 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• rusty-ci-0.9.6 test passed test failed
  UB in linked_hash_map

• rusty-yaml-0.4.3 test passed test failed
  UB in linked_hash_map

• rvs-0.4.1 test passed test failed
  UB in linked_hash_map

• selenite-0.2.0 test passed test failed
  UB in linked_hash_map

• semvercli-0.0.1 test passed test failed
  UB in linked_hash_map

• seq_io-0.3.0 test passed test failed
  Depends on old crossbeam-epoch, author notified.

• serde-avro-0.5.0 test passed test failed
  UB in linked_hash_map; needs dependency bump but repo link is dead

• serde-hjson-0.9.1 test passed test failed
  UB in linked_hash_map; needs dependency bump, author notified.

• serde-protobuf-0.8.1 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• serde_yaml-0.8.11 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet
  PR merged to update linked_hashmap dependency to ^0.5.3, waiting on release

• serialport-3.3.0 test passed test failed
  Something timed out,spurious.

• shack-0.1.1 test passed test failed
  EOF in the database? possibly tests are not concurrency-compatible.

• sheesy-vault-4.0.7 test passed test failed
  UB in linked_hash_map (with semver-compatible fix)

• shyaml-0.4.1 test passed test failed
  UB in linked_hash_map (with semver-compatible fix)

• sled-search-0.2.0 test passed test failed
  Depends on old sled which saw a bunch of "uninitialized" fixes recently

• smartpool-0.3.2 test passed test failed
  Timing gone wrong

• softposit-0.3.9 test passed test failed
  Failing test uses an RNG

• sortuniq-0.1.0 test passed test failed
  UB in LRU that has been fixed upstream; author notified

• specs_time-0.6.1 test passed test failed
  UB in crossbeam-epoch 0.7.1, crate author notified

• strict-yaml-rust-0.1.1 test passed test failed
  UB in linked_hash_map (with semver-compatible fix)

• supervisor-rs-0.6.0 test passed test failed
  UB in linked_hash_map (with semver-compatible fix)

• sv-0.1.11 test passed test failed
  UB in linked_hash_map (with semver-compatible fix)

• symbolic-debuginfo-7.2.0 test passed test failed
  UB in dmsort which has been reported a while back already.

• test-patience-0.1.1 test passed test failed
  Timing failure

• text-0.0.4 test passed test failed
  UB in truetype

• tfs-0.1.3 test passed test failed
  UB in old crossbeam. Repository dead for 4 years so I did not bother with a bugreport.

• timekeeper-0.3.2 test passed test failed
  Timing-dependent failure.

• tin-drummer-1.0.1 test passed test failed
  UB in old crossbeam. Repository link dead.

• tokio-lock-1.1.0 test passed test failed
  UB in Tokio. Author notified.

• tokio-proto-0.1.1 test passed test failed
  Looks like a concurrency thing.

• toml_edit-0.1.5 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• toql_derive-0.1.4 test passed test failed
  Flaky test (even the code says so)

• trigger-1.1.1 test passed test failed
  UB in linked-hash-map, semver-compatible fix

• ttl_cache-0.5.1 test passed test failed
  UB in linked-hash-map, semver-compatible fix

• uncover-0.1.1 test passed test failed
  Looks very unrelated

• vcontrol-0.3.4 test passed build failed
  UB in linked-hash-map, semver-compatible fix

• viperus-0.1.10 test passed test failed
  UB in linked-hash-map, semver-compatible fix

• vivid-0.5.0 test passed test failed
  UB in linked-hash-map, semver-compatible fix

• vst-0.2.0 test passed test failed
  UB in crate which is fixed but no release yet.

• wcnt-0.4.0 test passed test failed
  UB in linked-hash-map, semver-compatible fix

• webauthn-rs-0.1.4 test passed test failed
  UB in LRU that has been fixed upstream. author notified

• wither-0.8.0 test failed build failed
  UB in linked-hash-map

• wood-0.4.2 test passed test failed
  UB in crate, fixed in git and there was a release since then

• workpool-0.1.1 test passed test failed
  UB in crossbeam-epoch 0.6.1; author notified

• yaml-merge-keys-0.4.0 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• yaml-rust-0.4.3 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• yaml-validator-0.1.0 test passed test failed
  UB in linked-hash-map, fixed upstream but no fix released yet

• ymlctx-0.1.8 test passed test failed
  UB in linked-hash-map, fix is semver-compatible

• zerobuf-0.0.2 test passed test failed
  UB in crate, reported