https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #6 from Julian Seward <jsew...@acm.org> --- > Model name: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Hmm, nothing particularly exotic there. > Sorry this is proving more troublesome than I expected. It's OK; however; we can't fix it if we can't reproduce it. Can you maybe re-check your testing setup? TBH I seriously doubt that Massif or the V framework as a whole mishandles memchr, since I've run huge apps (eg, Firefox) on Massif and I see no such breakage. Plus there are multiple auto-test runs every night, on various F35 targets, and I'm not aware of such breakage in them. That said it maybe that you've fallen across some obscure corner case that is broken. But I can't imagine what that could be. -- You are receiving this mail because: You are watching all bug changes.
