[issue22668] memoryview.format is corrupted due to dangling shared pointer

Stefan Krah added the comment: Thanks, David. The tests assumed little-endian, which is now fixed. The MemoryError is sporadic and unrelated -- the OpenIndiana bot often has system load issues. I don't see any more related failures, please reopen if you do. :) -- status: open -> close

[issue22668] memoryview.format is corrupted due to dangling shared pointer

Roundup Robot added the comment: New changeset 9a4af12dcc9d by Stefan Krah in branch '3.4': Issue #22668: Remove endianness assumption in test. https://hg.python.org/cpython/rev/9a4af12dcc9d New changeset da0ca7b1351f by Stefan Krah in branch 'default': Issue #22668: Merge from 3.4. https://hg.p

[issue22668] memoryview.format is corrupted due to dangling shared pointer

R. David Murray added the comment: The buildbots aren't happy. This one errors in the added test: http://buildbot.python.org/all/builders/System%20Z%20Linux%203.x/builds/2595/steps/test/logs/stdio Another one had a MemoryError in lib2to3 tests. Not sure what is going on, but the one above at

[issue22668] memoryview.format is corrupted due to dangling shared pointer

Roundup Robot added the comment: New changeset e9c1fca50b46 by Stefan Krah in branch '3.4': Issue #22668: Ensure that format strings survive slicing after casting. https://hg.python.org/cpython/rev/e9c1fca50b46 New changeset 37112bd3dfb3 by Stefan Krah in branch 'default': Closes #22668: Merge f

[issue22668] memoryview.format is corrupted due to dangling shared pointer

Stefan Krah added the comment: Thanks for the detailed report! Making a private copy of 'format' for each memoryview generally sounds like the best solution. However, format strings can be arbitrarily large, so we'd need to store the copy in the ob_array after shape, strides and suboffsets. Th

[issue22668] memoryview.format is corrupted due to dangling shared pointer

Changes by Berker Peksag : -- stage: -> patch review versions: -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue22668] memoryview.format is corrupted due to dangling shared pointer

Tom Flanagan added the comment: Fix memoryview object allocations to copy format string -- keywords: +patch Added file: http://bugs.python.org/file36966/22668patch.diff ___ Python tracker __

[issue22668] memoryview.format is corrupted due to dangling shared pointer

New submission from Tom Flanagan: When slicing or cloning a memoryview object that has been previously cast to change its format string, the new memoryview's format shares a pointer to the parent's format string, which may be deleted at any time. This manifests as a corrupt format when using t