Amalgam 54.3.14

What's Changed

• 21473: Fixes segfault caused by setting a number type on a null, cleans up code around setting EN to number values by @howsohazard in #256

Full changelog: 9da9cb0...86aa237

Amalgam 54.3.13

What's Changed

• 21437: Fixes crash when specifying invalid label to get_entity_comments by @howsohazard in #247

• 21446: Opcodes get_entity_rand_seed and get_entity_root_permissions no longer require an entity, numerous stability fixes by @howsohazard in #248

• 21448: Addresses inconsistencies in ThreadPool, potentially improving stability and performance by @howsohazard in #249

• 21453: Fixes numerous issues in concurrency that could lead to instability and crashes by @howsohazard in #250

• 21454: Fixes rare segfault in tight concurrency situations by @howsohazard in #252

• 21456: Improves AFMI at detecting memory issues by @howsohazard in #253

• 21455: Fixes potential memory corruption issues by @howsohazard in #254

• 21466: Fixes possible segfault when retrieving target, makes AMI work with multithreading by @howsohazard in #255

Full changelog: 73930f9...9da9cb0

Amalgam 54.3.12

What's Changed

• 21422: Reduces likelihood of erroneous node in opcode stack, method renames for cleanup by @howsohazard in #246

Full changelog: 5327844...73930f9

Amalgam 54.3.11

What's Changed

• 21413: Fixes segfaults by @howsohazard in #245

Full changelog: bb59ce2...5327844

Amalgam 54.3.10

What's Changed

• 21412: Fixes race condition with nested concurrency by @howsohazard in #244

Full changelog: b77b0d2...bb59ce2

Amalgam 54.3.9

What's Changed

• 21373: Fixes race condition where garbage collection could occur while tasks were being enqueued. Also minor code cleanup by @howsohazard in #243

Full changelog: 5e88a91...b77b0d2

Amalgam 54.3.8

What's Changed

• 21323: Fixes compilation errors when defining USE_STL_HASH_MAPS by @apbassett in #240

• 21338: Fixes potential segfaults by @howsohazard in #241

• 21350: Tightens cycle check propagation, makes mark part of GC more robust to deallocated memory, renames interpreter node stack for clarity by @howsohazard in #242

Full changelog: 35de34b...5e88a91

Amalgam 54.3.7

What's Changed

• 21319: Fixes redundant allocations in accum by @howsohazard in #238

• 21320: Fixes stability issues with accum_to_entities and retrieve opcodes by @howsohazard in #239

Full changelog: 0776158...35de34b

Amalgam 54.3.6

What's Changed

• 21263: Adds performance counters for memory writes that affect uniqueness of results by @howsohazard in #228

• 21277: Fixes bugs with rewrite by @howsohazard in #229

• 21278: Fixes bug where remove opcode would crash if given invalid input by @howsohazard in #230

• 21287: Fixes issues with rewrite by @howsohazard in #231

• 21295: Fixes another issue in rewrite by @howsohazard in #232

• 21307: Adds validation upon entity destruction when built with AMALGAM_FAST_MEMORY_INTEGRITY by @howsohazard in #233

• 21311: Improves consistency of accum opcode and fixes issues with concurrent access by @howsohazard in #235

• 21312: Fixes false positive memory issues detected where setting need cycles does not apply for assign/accum by @howsohazard in #236

• 21315: Fixes potential crashes with accum and multithreading by @howsohazard in #237

Full changelog: 5cf8f8f...0776158

Amalgam 54.3.5

What's Changed

• 21250: Fixes issues with call_sandboxed and constrained call_entities, improves debugging instrumentation by @howsohazard in #223

• 21258: Catches erroneously accessed, deallocated nodes faster by @howsohazard in #224

• 21255: Fixes possible segfault, fixes some spelling mistakes by @howsohazard in #225

• 21262: Fixes potential seg faults and improves performance by tracking side effects (memory writes) that can affect uniqueness of nodes by @howsohazard in #226

• 21264: Fixes potential issues with concurrent filter and nested concurrency by @howsohazard in #227

Full changelog: 66b74eb...5cf8f8f