[issue5614] Malloc errors in test_io

[Ronald Oussoren]

Ronald Oussoren  added the comment:

The error is printed by libc, there's nothing we can do about that.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[William Schwartz]

William Schwartz  added the comment:

In Jupyter Notebook, I tried to pass a large amount of data (about 2.3 GB) to 
Statsmodels's KDEUnivariate.fit 
(https://www.statsmodels.org/dev/generated/statsmodels.nonparametric.kde.KDEUnivariate.fit.html#statsmodels.nonparametric.kde.KDEUnivariate.fit)
 with kernel='cos'. In the Notebook, I got a MemoryError exception and 
traceback (which unfortunately I have since lost).

In the terminal where I was running the Jupyter server, the Python 3.7 kernel 
spat out:

Python(86244,0x7fff91104380) malloc: *** mach_vm_map(size=465845322670080) 
failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

The MemoryError coming up in the Notebook interface is the correct behavior, 
but I wanted to bring to your attention that the malloc junk on stderr happens 
even outside of Python's tests.

I'm on macOS 10.13.5.

--
components: +macOS
nosy: +William.Schwartz
versions: +Python 3.7 -Python 3.1

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Ronald Oussoren]

Ronald Oussoren ronaldousso...@mac.com added the comment:

Closing the issue as this is not a bug in python (as noted in the 
comments) and there doesn't seem to be a workaround for avoiding the 
spurious messages on stderr.

--
resolution:  - wont fix
status: open - closed
type: crash - behavior

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Ronald Oussoren]

Ronald Oussoren ronaldousso...@mac.com added the comment:

What's more annoying: the error goes away while running in a debugger.

The issue happens at least in tes_constructor:

test_constructor (__main__.CBufferedWriterTest) ... 
python.exe(35957,0x7fff701d1720) malloc: *** mmap(size=-
9223372036854775808) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
ok

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Ronald Oussoren]

Ronald Oussoren ronaldousso...@mac.com added the comment:

Buffer_size is set to 0x7fff in BufferedWriter_init at the end 
of test_constructor.

I have no idea why this happens, but this definitly seems wrong to me. 
Debugging is rather hard at the moment because the issue goes away in the 
debugger.

Setting this as a release blocker because arguments of a wrong magnitude 
to memory allocation functions are scary.

--
priority:  - release blocker
stage:  - needs patch
type:  - crash

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Hirokazu Yamamoto]

Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment:

malloc: *** mmap(size=-9223372036854775808) failed

Does this error occur even if you revert Modules/mmapmodule.c to ｒ69214?
I have touched this module recently (I believe I fixed only SEGV bugs,
not changed behavior) so I want to know it.

--
nosy: +ocean-city

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Ronald Oussoren]

Ronald Oussoren ronaldousso...@mac.com added the comment:

I don't think this is related to Python's mmap module, the message says 
that malloc(3) cannot mmap some extra memory space.

I'll test with the older version of mmap just in case.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Hirokazu Yamamoto]

Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment:

Sorry, this is not related to mmap module... Forgot my comments.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Hirokazu Yamamoto]

Changes by Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp:


--
nosy:  -ocean-city

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

If you look at test_io, calling malloc() with sys.maxsize is precisely
the purpose of the test, to check that allocation failures are detected
and reported properly. So the warnings can be safely ignored, if they
only happen in test_constructor.

--
nosy: +pitrou
priority: release blocker - normal
versions: +Python 3.1

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

PS: if the warnings are annoying, the test can be disabled selectively
under Mac OS X.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5614] Malloc errors in test_io

[Ronald Oussoren]

Ronald Oussoren ronaldousso...@mac.com added the comment:

I can't believe that I completely missed that this is the purpose of the 
tests, I honestly believed that I had checked everything there was to 
check :-(

Disabling the test won't be necessary, I'm keeping this issue open for a 
while longer to check if we can avoid getting a message on stderr during 
the test. It's rather annoying that malloc logs error messages during what 
turns out to be perfectly fine behaviour.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5614
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com