Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in `python': double free or corruption (out): 0x00007fb048000d00 #94134

Closed
Aarif1430 opened this issue Jun 22, 2022 · 3 comments
Closed
Labels
type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@Aarif1430
Copy link

Aarif1430 commented Jun 22, 2022

Crash report
One of my server jobs was processing a data file and the program got crashed in middle.

Error messages
Error in `python': double free or corruption (out): 0x00007fb10048000d00

Your environment

  • CPython versions tested on: rhel-py39-64bit-gcc1 (Python3.9.5)
  • Operating system and architecture: redhat enterprise version 6
@Aarif1430 Aarif1430 added the type-crash A hard crash of the interpreter, possibly with a core dump label Jun 22, 2022
@sweeneyde
Copy link
Member

Do you have a stackdump or some kind of reproducer? Without anything to go off of, there's not much we can do.

@Aarif1430
Copy link
Author

Unfortunately, I can't paste or copy the original stack dump from the remote machine due to access rights. However, I saw someone has raised the same issue in python3.6. Here is the link

@sweeneyde
Copy link
Member

Can you describe anything about the sort of program? Are you using any extension modules? Threads? Multiprocessing? Asyncio? Numpy? Pandas? Is it reliably reproducable, or was it a one-time thing? If it's repeatable, can you try to pare it down to a short program? Without the ability to reproduce it, I don't see anything that can be done. Does it still happen if you update to python 3.10?

Do you have evidence that that other issue is related? Double frees are an unspecific and common bug in C programs.

@sweeneyde sweeneyde added the pending The issue will be closed if no feedback is provided label Jun 23, 2022
@hauntsaninja hauntsaninja closed this as not planned Won't fix, can't repro, duplicate, stale Jul 6, 2022
@erlend-aasland erlend-aasland removed the pending The issue will be closed if no feedback is provided label Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-crash A hard crash of the interpreter, possibly with a core dump
Projects
None yet
Development

No branches or pull requests

4 participants