Same problem after updating Unity from 2022.3.58f1 to 2022.3.62f2

Issue says this is Fixed in 6000.0.59f1. I did the same as others in this thread (Spawnterminator) and updated to latest version, in hope that it was fixed. In my case I updated to 6000.0.60f1 and the issue is still there. Unsure if I should try 6000.0.59f2, as it is a lower version.

We're now seeing a lot of this among our players on 6000.1.17f1, after upgrading due to the security vulnerability issue.

Follow Up...

Ok, I took the risk ( got impatient for a response, sorry), and downloaded 6000.0.59f2 from the download archive, thinking perhaps the fix I'm looking for is actually in 6000.0.59f1 and 6000.0.59f1 was rolled into 6000.0.59f2, before 6000.0.59f1 could be released (because of the recently discovered vulnerability issue, hence no release notes.

This is on the download archive:
https://unity.com/releases/editor/whats-new/6000.0.59f2#installs

There is no entry for:
https://unity.com/releases/editor/whats-new/6000.0.59f1#installs
So I can't read the release notes, and I can't find any release info about this version online anywhere.

Anyway, downloaded 6000.0.59f2, ran my game, and no Memory leak warnings. Or any other warnings for that matter. :-)

Thanks for resolving this issue
Richard

The issue tracker says that this issue is fixed, and today Unity released 6000.0.59f2. I have read through the release notes,

https://unity.com/releases/editor/whats-new/6000.0.59f2#installs

And there is no mention of this being fixed in 6000.0.59f2, even though the issue is fixed in 6000.0.59f1.

I upgraded to 6000.0.58f2 when I received the email from Unity warning of the recently found vulnerability issue with Unity, so I downloaded the new version, opened my project, and I experienced this bug immediately in my game, and then took the rest of the day to debug the issue only, to then find out this is a known bug and would be fixed in 6000.0.59f2. Great, I thought I would wait for 6000.0.59f2, and everything will be great.

But no. :(
No mention of this issue in the release notes for 6000.0.59f2.

Can we get clarification as to what version this fix will be rolled into?

Many Thanks
Richard

NOT FIXED. 6000.2.6f2.

ParallelBitArray in InstanceCuller.CreateSceneViewHiddenObjectsCullingJob_EditorOnly (package com.unity.render-pipelines.core)

Assertion failed
UnityEngine.Rendering.CullSceneViewHiddenRenderersJob:Execute (int)
Unity.Jobs.IJobParallelForExtensions/ParallelForJobStruct`1<UnityEngine.Rendering.CullSceneViewHiddenRenderersJob>:Execute (UnityEngine.Rendering.CullSceneViewHiddenRenderersJob&,intptr,intptr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,int)

I am using particle system and started seeing this error after updating from 6000.0.32f1 to 6000.0.58f2. I updated due to the security vulnerability notice.

Plus one. I updated to the latest Unity 6.0 (6000.0.58f2) patch due to security vulnerability and I am now seeing this issue (was not seeing it before).

I had to update from 6000.0.13f to 6000.0.17f due to a recent Vulnerability bug found on older versions. Now I am getting this error quite frequently.

Exists in 6000.5.56, 57 and 58. It says fix in review for .59. Waiting for the fix, or perhaps revert to an older version? can't ship like this. happens in 2D URP on all particle systems in the game. Much less on .58 than previous versions but still happens.