[issue26797] Segafault in _PyObject_Alloc

STINNER Victor added the comment: > Closing this one. Haven't seen this in a while, probably it was a bug in > libuv. I told you so! :-D -- ___ Python tracker ___ _

[issue26797] Segafault in _PyObject_Alloc

Yury Selivanov added the comment: Closing this one. Haven't seen this in a while, probably it was a bug in libuv. -- resolution: -> works for me stage: test needed -> resolved status: open -> closed ___ Python tracker

[issue26797] Segafault in _PyObject_Alloc

Yury Selivanov added the comment: > Did you check your code using a debug build, PYTHONDEBUG=debug (if CPython is compiled in release mode), or PYTHONMALLOC=malloc + valgrind? (The env var requires CPython 3.6) Can't reproduce it in the debug build :( Since I'm not writing C by hand (I use Cyth

[issue26797] Segafault in _PyObject_Alloc

STINNER Victor added the comment: Usually a "bug in the memory allocator" means a buffer overflow in your code. Did you check your code using a debug build, PYTHONDEBUG=debug (if CPython is compiled in release mode), or PYTHONMALLOC=malloc + valgrind? (The env var requires CPython 3.6) -

[issue26797] Segafault in _PyObject_Alloc

Changes by Ned Deily : -- nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue26797] Segafault in _PyObject_Alloc

New submission from Yury Selivanov: I'm working on an implementation of asyncio event loop on top of libuv [1]. One of my tests crashes on Mac OS X with a segfault [2]. The problem is that it's not consistent -- looks like it depends on size of uvloop so binary, or/and amount of objects allo