Log output flood with malloc() of large size

[monni]

hrev58314

malloc() of 7809071836364276279 bytes asked
Last message repeated 14 times.
Last message repeated 16 times.
...

Doesn't throw to KDL or Debugger, but doesn't print more useful information either.

[waddlesplash]

This message comes from libroot. You could turn it into a debugger() call and see what's calling it (probably some third-party application).

[monni]

960: DEBUGGER: malloc() of large size asked!
debug_server: Thread 960 entered the debugger: Debugger call: `malloc() of large size asked!'
slab memory manager: created area 0xffffffffae801000 (35296)
stack trace, current PC 0x1f82017b399  </boot/system/non-packaged/lib/libroot.so> _kern_debugger + 0x9:
  (0x7f55b452ebf0)  0x1f820203661  </boot/system/non-packaged/lib/libroot.so> malloc + 0x91
  (0x7f55b452ec20)  0xdb9005ea58  </boot/system/lib/libpython3.9.so.1.0> PyObject_Malloc + 0xd8
  (0x7f55b452ec40)  0xdb9003a6c5  </boot/system/lib/libpython3.9.so.1.0> PyBytes_FromStringAndSize + 0x75
  (0x7f55b452ec70)  0xdb901336f8  </boot/system/lib/libpython3.9.so.1.0> _io__Buffered_read + 0x288
  (0x7f55b452ece0)  0xdb9005c9be  </boot/system/lib/libpython3.9.so.1.0> cfunction_vectorcall_FASTCALL + 0x5e
  (0x7f55b452ed20)  0xe5d84fe5ee  </boot/system/lib/python3.9/lib-dynload/_pickle.cpython-39.so> _Pickle_FastCall + 0x4e
  (0x7f55b452ed70)  0xe5d850156d  </boot/system/lib/python3.9/lib-dynload/_pickle.cpython-39.so> _Unpickler_ReadImpl + 0xcd
  (0x7f55b452edb0)  0xe5d85057f5  </boot/system/lib/python3.9/lib-dynload/_pickle.cpython-39.so> load + 0x1bf5
  (0x7f55b452ee20)  0xe5d8506922  </boot/system/lib/python3.9/lib-dynload/_pickle.cpython-39.so> _pickle_load + 0x252
  (0x7f55b452eeb0)  0xdb9005c765  </boot/system/lib/libpython3.9.so.1.0> cfunction_vectorcall_FASTCALL_KEYWORDS + 0x65
  (0x7f55b452eef0)  0xdb90092d92  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x4fe2
  (0x7f55b452f020)  0xdb9003e2b2  </boot/system/lib/libpython3.9.so.1.0> function_code_fastcall + 0xa2
  (0x7f55b452f050)  0xdb9003f9b6  </boot/system/lib/libpython3.9.so.1.0> method_vectorcall + 0x76
  (0x7f55b452f0e0)  0xdb90092d92  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x4fe2
  (0x7f55b452f210)  0xdb9008d2fc  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalCode + 0x2bc
  (0x7f55b452f2c0)  0xdb9003e10c  </boot/system/lib/libpython3.9.so.1.0> _PyFunction_Vectorcall.localalias + 0xec
  (0x7f55b452f360)  0xdb9008e4c0  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x710
  (0x7f55b452f490)  0xdb9003e2b2  </boot/system/lib/libpython3.9.so.1.0> function_code_fastcall + 0xa2
  (0x7f55b452f4c0)  0xdb9003d59c  </boot/system/lib/libpython3.9.so.1.0> _PyObject_FastCallDictTstate + 0xbc
  (0x7f55b452f520)  0xdb9003e7f8  </boot/system/lib/libpython3.9.so.1.0> _PyObject_Call_Prepend + 0x68
  (0x7f55b452f5b0)  0xdb9006dbee  </boot/system/lib/libpython3.9.so.1.0> slot_tp_init + 0x6e
  (0x7f55b452f600)  0xdb9006aceb  </boot/system/lib/libpython3.9.so.1.0> type_call + 0xfb
  (0x7f55b452f630)  0xdb9003d8a3  </boot/system/lib/libpython3.9.so.1.0> _PyObject_MakeTpCall + 0x73
  (0x7f55b452f680)  0xdb90092e79  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x50c9
  (0x7f55b452f7b0)  0xdb9008d2fc  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalCode + 0x2bc
  (0x7f55b452f860)  0xdb9003e10c  </boot/system/lib/libpython3.9.so.1.0> _PyFunction_Vectorcall.localalias + 0xec
  (0x7f55b452f900)  0xdb9008e4c0  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x710
  (0x7f55b452fa30)  0xdb9008d2fc  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalCode + 0x2bc
  (0x7f55b452fae0)  0xdb9003e10c  </boot/system/lib/libpython3.9.so.1.0> _PyFunction_Vectorcall.localalias + 0xec
  (0x7f55b452fb80)  0xdb9008e4c0  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x710
  (0x7f55b452fcb0)  0xdb9003e2b2  </boot/system/lib/libpython3.9.so.1.0> function_code_fastcall + 0xa2
  (0x7f55b452fce0)  0xdb9003d59c  </boot/system/lib/libpython3.9.so.1.0> _PyObject_FastCallDictTstate + 0xbc
  (0x7f55b452fd40)  0xdb9003e7f8  </boot/system/lib/libpython3.9.so.1.0> _PyObject_Call_Prepend + 0x68
  (0x7f55b452fdd0)  0xdb9006dbee  </boot/system/lib/libpython3.9.so.1.0> slot_tp_init + 0x6e
  (0x7f55b452fe20)  0xdb9006aceb  </boot/system/lib/libpython3.9.so.1.0> type_call + 0xfb
  (0x7f55b452fe50)  0xdb9003ec2d  </boot/system/lib/libpython3.9.so.1.0> _PyObject_Call + 0x7d
  (0x7f55b452fe90)  0xdb90091518  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalFrameDefault + 0x3768
  (0x7f55b452ffc0)  0xdb9008d2fc  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalCode + 0x2bc
  (0x7f55b4530070)  0xdb9008d039  </boot/system/lib/libpython3.9.so.1.0> _PyEval_EvalCodeWithName + 0x49
  (0x7f55b45300d0)  0xdb9008cfe0  </boot/system/lib/libpython3.9.so.1.0> PyEval_EvalCodeEx + 0x40
  (0x7f55b4530140)  0xdb900ff7ac  </boot/system/lib/libpython3.9.so.1.0> PyEval_EvalCode + 0x1c
  (0x7f55b4530180)  0xdb90110ec6  </boot/system/lib/libpython3.9.so.1.0> run_eval_code_obj + 0x56
  (0x7f55b45301c0)  0xdb90110e4d  </boot/system/lib/libpython3.9.so.1.0> run_mod + 0x6d
  (0x7f55b45301f0)  0xdb8ffebb64  </boot/system/lib/libpython3.9.so.1.0> pyrun_file + 0xc7
  (0x7f55b4530240)  0xdb8ffeb882  </boot/system/lib/libpython3.9.so.1.0> PyRun_SimpleFileExFlags + 0x380
  (0x7f55b45302c0)  0xdb90118999  </boot/system/lib/libpython3.9.so.1.0> Py_RunMain + 0x2c9
  (0x7f55b4530390)  0xdb901185a9  </boot/system/lib/libpython3.9.so.1.0> Py_BytesMain + 0x29
  (0x7f55b45303c0)  0xca59b5d66e  </boot/system/bin/python3.9> _start + 0x3e
  (0x7f55b45303f0)  0xfed8efae95  </boot/system/runtime_loader> runtime_loader + 0x115

[waddlesplash]

So, it's from Python then. Not a Haiku problem.