(In reply to Bugmon [:jkratzer for issues] from comment #7) > Pernosco is only supported for Linux x86_64 bugs. I'm guessing this was Bugmon picking up on the `Platform: Windows` field at the top of this bug. (I do see that comment 0 was on Windows, per the `.dll` suffixes in the backtrace there) Jason, if it's not too much trouble, could you see if you can get this to crash on Linux as well? I don't know if there's any reason this should be Windows-specific, aside from maybe the particulars of font metrics & things like that (if the testcase has any sort of implicit dependency on that). If that were the only thing making this Windows-specific, I'd hope that the fuzzers would be able to discover approriate lenghts/etc. to trigger the same issue on other platforms. (The motivation would be to get this in pernosco if possible, since that makes fuzzer bugs much easier to reason about and debug.)
Bug 1868190 Comment 14 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 Bugmon [:jkratzer for issues] from comment #7) > Pernosco is only supported for Linux x86_64 bugs. I'm guessing this was Bugmon picking up on the `Platform: Windows` field at the top of this bug. (I do see that comment 0 was on Windows, per the `.dll` suffixes in the backtrace there) Jason, if it's not too much trouble, could you see if you can get this to crash on Linux as well? I don't know if there's any reason this should be Windows-specific, aside from maybe the particulars of font metrics & things like that (if the testcase has any sort of implicit dependency on that). If that were the only thing making this Windows-specific, I'd hope that the fuzzers would be able to discover appropriate lengths/etc. to trigger the same issue on other platforms. (The motivation would be to get this in pernosco if possible, since that makes fuzzer bugs much easier to reason about and debug.)