[issue12340] Access violation when using the C version of the io module

Changes by Serhiy Storchaka : -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python tracker ___

[issue12340] Access violation when using the C version of the io module

Serhiy Storchaka added the comment: Looks as the crash was fixed in one of previous bugfixes. As for memoryview related issue, this is a duplicate of issue20699. -- nosy: +serhiy.storchaka status: languishing - pending superseder: - Behavior of ZipFile with file-like object and

[issue12340] Access violation when using the C version of the io module

Christian Heimes added the comment: The issue hasn't seen an update for over two years. Were you able to solve the issue? -- nosy: +christian.heimes status: open - languishing ___ Python tracker rep...@bugs.python.org

[issue12340] Access violation when using the C version of the io module

OscarL added the comment: I can't reproduce the access violation on Windows, using Python 2.7.3. Using the test_bufio.py script by santa4nt, I can see that the fail still happens. As Santoso Wijaya (santa4nt) said in a previous comment: The `write(data)` method is getting a `memoryview`

[issue12340] Access violation when using the C version of the io module

Santoso Wijaya santoso.wij...@gmail.com added the comment: As for the memory at %p string, when _io.BufferedWriter prepares the byte buffer into a PyMemoryView wrapper and passes it into the raw IO object: res = PyObject_CallMethodObjArgs(self-raw, _PyIO_str_write, memobj, NULL); For some

[issue12340] Access violation when using the C version of the io module

Santoso Wijaya santoso.wij...@gmail.com added the comment: Note: Removing threading call (lock acquire, release) would remove the crash, but still triggers the memory at %p conversion of PyMemoryView. -- ___ Python tracker rep...@bugs.python.org

[issue12340] Access violation when using the C version of the io module

Changes by Santoso Wijaya santoso.wij...@gmail.com: Added file: http://bugs.python.org/file22380/test_bufio_nothreading.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12340 ___

[issue12340] Access violation when using the C version of the io module

Santoso Wijaya santoso.wij...@gmail.com added the comment: If `write(self, data)` is expected to receive `data` as a memoryview object, then it's up to pyserial to use `data.tobytes()` instead of `bytes(data)`, though this does not seem to be documented in the io module doc. --

[issue12340] Access violation when using the C version of the io module

New submission from OscarL oscar.le...@gmail.com: This is on Windows XP SP2. Using Python 2.7.1 and 2.7.2. While executing the unit tests of the PySerial package, version 2.5 (http://pypi.python.org/pypi/pyserial) one of the tests fails when using the C version of the io module (io), but pass

[issue12340] Access violation when using the C version of the io module

Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12340 ___ ___ Python-bugs-list

[issue12340] Access violation when using the C version of the io module

Santoso Wijaya santoso.wij...@gmail.com added the comment: Regarding the crash, From what I can see, the `tp_clear` method of bufferedrwpair is called during Py_Finalize() that leads to garbage collection. This NULLs `self-writer` for the rwpair object. Later, in the same garbage collection

[issue12340] Access violation when using the C version of the io module

Benjamin Peterson benja...@python.org added the comment: Can you produce a self-contained test case? -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12340 ___