[issue15994] memoryview to freed memory can cause segfault

Change by Inada Naoki : -- nosy: +inada.naoki ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue15994] memoryview to freed memory can cause segfault

Change by JP Sugarbroad : -- nosy: +taralx ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue15994] memoryview to freed memory can cause segfault

Change by Gregory P. Smith : -- nosy: +gregory.p.smith versions: +Python 3.7, Python 3.8 -Python 3.5 ___ Python tracker ___ ___ Pyth

[issue15994] memoryview to freed memory can cause segfault

Changes by Evgeny Kapun : -- nosy: +abacabadabacaba ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue15994] memoryview to freed memory can cause segfault

Martin Panter added the comment: I think idea 2 (error if memoryview not released) would not work. It would rely on garbage collection, which is not always immediate. E.g. if the memoryview were kept alive by a reference cycle, it may not immediately be released. I don’t think idea 3 is worthw

[issue15994] memoryview to freed memory can cause segfault

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue15994] memoryview to freed memory can cause segfault

Martin Panter added the comment: I recently created Issue 26720 about a similar situation with BufferedWriter. However I am starting to believe that the problem cannot be solved the way I originally wanted. Instead, the best solution there would be similar what I would suggest here: we need to

[issue15994] memoryview to freed memory can cause segfault

Stefan Krah added the comment: > But I think there should be some way of guaranteeing that a memoryview will > not try to access memory which has already been freed. Unless the "buffered *self" parameter in _buffered_raw_read() is made a full PEP-3118 exporter, I'm not sure how it would be poss

[issue15994] memoryview to freed memory can cause segfault

Martin Panter added the comment: Saving a reference to the overall buffered reader is probably not good enough. I think the buffer is freed when close() is called, so a reference to this internal buffer would need to be saved instead (or as well). Unless we stop having close() free the buffer.

[issue15994] memoryview to freed memory can cause segfault

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15994] memoryview to freed memory can cause segfault

Changes by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue15994] memoryview to freed memory can cause segfault

Stefan Krah added the comment: We deal with it when we have time. IMO there is little value in bumping up issues this way. -- ___ Python tracker ___

[issue15994] memoryview to freed memory can cause segfault

Mark Lawrence added the comment: Can someone follow this up noting it refers to #15903. -- nosy: +BreamoreBoy ___ Python tracker ___ _

[issue15994] memoryview to freed memory can cause segfault

Changes by Christian Heimes : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue15994] memoryview to freed memory can cause segfault

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15994] memoryview to freed memory can cause segfault

New submission from Richard Oudkerk: A memoryview which does not own a reference to its base object can point to freed or reallocated memory. For instance the following segfaults for me on Windows and Linux. import io class File(io.RawIOBase): def readinto(self, buf): global vie