[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #13 from Rhys Kidd --- Any changes for macOS can come later. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Julian Seward changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Julian Seward changed: What|Removed |Added CC||rhysk...@gmail.com ---

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Ivo Raisr changed: What|Removed |Added Attachment #105549|0 |1 is obsolete|

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #8 from Tom Hughes --- Fails at 32Gb without patch: trying for 31 GB .. ==12078== Warning: set address range perms: large range [0x3960c040, 0x7f960c040) (defined) .. OK ==12078== Warning: set address range perms: large

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #7 from Julian Seward --- Created attachment 105549 --> https://bugs.kde.org/attachment.cgi?id=105549=edit Proposed fix (so far, Linux only) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #6 from Julian Seward --- Created attachment 105548 --> https://bugs.kde.org/attachment.cgi?id=105548=edit test case (allocgig.c) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #5 from Julian Seward --- I had hoped to do this for 3.12.0, but after looking at the #ifdef swamp in VG_(am_startup) that sets aspacem_maxAddr, I think it is too risky, because of the number of different cases that need to

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #4

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #3 from Julian Seward --- The primary_map array, I mean. I didn't mean the whole 128GB needs to be zeroed out at startup. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #2 from Julian Seward --- In the trunk right now we have N_PRIMARY_BITS = 20, which according to the svn log makes the maximum usable memory amount be 64G. That was done at end-Jan 2013 and should surely be in 3.10 and

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1