[issue5614] Malloc errors in test_io

Ronald Oussoren added the comment: The error is printed by libc, there's nothing we can do about that. -- ___ Python tracker ___ ___

[issue5614] Malloc errors in test_io

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) w

[issue5614] Malloc errors in test_io

Ronald Oussoren 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 __

[issue5614] Malloc errors in test_io

Ronald Oussoren 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

[issue5614] Malloc errors in test_io

Antoine Pitrou added the comment: PS: if the warnings are annoying, the test can be disabled selectively under Mac OS X. -- ___ Python tracker ___ ___

[issue5614] Malloc errors in test_io

Antoine Pitrou 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

[issue5614] Malloc errors in test_io

Changes by Hirokazu Yamamoto : -- nosy: -ocean-city ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5614] Malloc errors in test_io

Hirokazu Yamamoto added the comment: Sorry, this is not related to mmap module... Forgot my comments. -- ___ Python tracker ___ ___ Py

[issue5614] Malloc errors in test_io

Ronald Oussoren 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

[issue5614] Malloc errors in test_io

Hirokazu Yamamoto 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:

[issue5614] Malloc errors in test_io

Ronald Oussoren 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. Setti

[issue5614] Malloc errors in test_io

Ronald Oussoren 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 (er

[issue5614] Malloc errors in test_io

New submission from Ronald Oussoren : The malloc warnings happen on OSX, with a fresh checkout of the python3 branch. Python was build using --enable-universalsdk=/ --with-universal- archs=all, on a x86_64 capable laptop running Leopard. The issue goes away when running from the commandline, th