Process finished with exit code -1073741819 (0xC0000005)

[fasami]

BPO	46839
Nosy	@zware, @eryksun

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2022-02-23.21:49:25.439>
created_at = <Date 2022-02-23.21:36:16.230>
labels = ['type-crash']
title = 'Process finished with exit code -1073741819 (0xC0000005)'
updated_at = <Date 2022-02-24.04:16:14.070>
user = 'https://bugs.python.org/fasami'

bugs.python.org fields:

activity = <Date 2022-02-24.04:16:14.070>
actor = 'eryksun'
assignee = 'none'
closed = True
closed_date = <Date 2022-02-23.21:49:25.439>
closer = 'zach.ware'
components = []
creation = <Date 2022-02-23.21:36:16.230>
creator = 'fa.sami'
dependencies = []
files = []
hgrepos = []
issue_num = 46839
keywords = []
message_count = 3.0
messages = ['413859', '413861', '413879']
nosy_count = 3.0
nosy_names = ['zach.ware', 'eryksun', 'fa.sami']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue46839'
versions = []

[fasami]

Hi,
I am running my python code for large data set and currently, I received this exit code: "Process finished with exit code -1073741819 (0xC0000005)"

I monitored via Event Viewer and found the following error. I wonder how I can solve this issue? Thanks

Faulting application name: python.exe, version: 0.0.0.0, time stamp: 0x56abcaee
Faulting module name: python27.dll, version: 2.7.11150.1013, time stamp: 0x56abcaed
Exception code: 0xc0000005
Fault offset: 0x00000000000a4f81
Faulting process id: 0x29d0
Faulting application start time: 0x01d8287ff03c7476
Faulting application path: C:\Users\sami\Anaconda2\python.exe
Faulting module path: C:\Users\sami\Anaconda2\python27.dll

[zware]

0xc0000005 appears to be an access violation, but beyond that there's not much we can help with here.

For a start, Python 2.7 has been out of support for over 2 years now, and as far as I can easily tell Anaconda2 is no longer supported either. It is highly recommended to update to Python 3.9 or later if at all possible.

Also, it seems likely that the problem is actually in a third-party extension module rather than Python itself, though it's impossible to tell for sure from what information is here.

For further assistance, you can try the Users category of discuss.python.org, the python-list@python.org mailing list, or a forum specific to Anaconda (though I'm not familiar with one myself).

[eryksun]

I tried to get more information for you by installing 2.7.11 (64-bit because of the given fault) and unassembling python27.dll at the fault offset. But it doesn't help. Whatever the bug is, it ended up jumping to an address that's in the middle of an instruction. This final bit of nonsense is what killed the process with an access violation, but it's not directly related to the problem.

Here's the address that triggered the access violation:

0:000> ? python27 + a4f81
Evaluate expression: 1368149889 = 00000000`518c4f81

The nearest function is rawiobase_readall():

0:000> ln python27 + a4f81
(00000000`518c4f10)   python27!rawiobase_readall+0x71   |
(00000000`518c51a0)   python27!resize_buffer

But 0x518c4f81 isn't the address of an instruction in this function:

0:000> u python27!rawiobase_readall python27!rawiobase_readall+80
python27!rawiobase_readall:
[...]
00000000`518c4f7f 48894318        mov     qword ptr [rbx+18h],rax
00000000`518c4f83 48894310        mov     qword ptr [rbx+10h],rax
00000000`518c4f87 48894320        mov     qword ptr [rbx+20h],rax
00000000`518c4f8b 48837f10fe      cmp     qword ptr [rdi+10h],0FFFFFFFFFFFFFFFEh
00000000`518c4f90 4c89642440      mov     qword ptr [rsp+40h],r12

It's inside of the first MOV instruction.