(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #5) > tsmith: Do you think this can be closed as WFM? Or, should keep open? There have been multiple reports of this issue with the latest being from last night (20241024-e509c25e4ec7). Because of the nature of this fuzzer it will required a different seed value to trigger the issue on different build (as mentioned be for each test will only work on the build it found the issue on). So just because the bug exists on a build doesn't mean it can be found the fuzzer/seed combo used with different build.
Bug 1924232 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #5) > tsmith: Do you think this can be closed as WFM? Or, should keep open? There have been multiple reports of this issue with the latest being from last night (20241024-e509c25e4ec7). Because of the nature of this fuzzer it will require a different seed value to trigger the issue on different build (as mentioned before each test will only work with the build it found the issue on). So just because the bug exists on a build doesn't mean it can be found the fuzzer/seed combo used with different build.