function contains of long loop each iteration it will do get data from different website using request.get and do analysis, loop will take one minute for 10 iteration.
after completed some 100 to 400 iteration it will exit with process finished with exit code -1073740940 (0xc0000374) do no what is this unexpected behavior!

Please include a minimal code snippet without external dependencies to reproduce the issue. Describe what you have done (script, traceback, operating system environment etc) and what you are expecting. Without these information it's unclear to debug a crash and especially if it's a bug in Python or the logic in the code.

Thanks

i am figuring out as heap memory issue because i am using multiple data frames and online web scrap data as well , may be memory is overloaded and it cause this issue .
please correct me it may not be changes or not.

I assume this is on Windows? 0xc0000374 is a heap corruption error on Windows.

I agree that without a way to reproduce this it will be impossible to track down any error.

You can enable faulthandler to get the Python traceback where the bug occurs. It might help a little bit. Either write the traceback into a file (file argument of faulthandler.enable()) or run your program in a terminal to see the traceback on the terminal.

http://docs.python.org/dev/library/faulthandler.html

I also suggest you to try to run your program using "python -X dev program.py" to enable more debug checks:
https://pythondev.readthedocs.io/debug_tools.html

PYTHONMALLOC=debug environment variable may help.

A crash with the code STATUS_HEAP_CORRUPTION (0xC0000374) is due to a bug, not memory exhaustion. The bug may not be the fault of the interpreter or standard library if you're working with extension modules or ctypes. It's easy to corrupt the internal structures of a heap. For example:

    >>> import ctypes
    >>> b = (ctypes.c_char * 100000)()
    >>> ctypes.POINTER(ctypes.c_int)(b)[-1] = 0
    >>> del b

[crashed]

    C:\>echo %errorlevel%
    -1073740940

Heap corruption is best examined with a debugger (e.g. windbg or cdb) attached to the faulting process, with full page heap checking enabled for the executable in the registry (usually set via gflags). This reserves a page before and after each heap allocation to ensure that writes that would otherwise corrupt the heap will instead immediately raise an access violation.

thanks Eryk Sun i am able to solve the problem, it was extension modules problem. it was helpful great.

Thanks guys for quick responses.  Eryk Sun  comment wa very help full.