Sudden death with SIGSEGV in RtlEnterCriticalSection

[dehex]

BPO	763190
Nosy	@facundobatista

^{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 2005-05-30.18:27:56.000>
created_at = <Date 2003-06-30.13:34:25.000>
labels = ['interpreter-core']
title = 'Sudden death with SIGSEGV in RtlEnterCriticalSection'
updated_at = <Date 2005-05-30.18:27:56.000>
user = 'https://bugs.python.org/dehex'

bugs.python.org fields:

activity = <Date 2005-05-30.18:27:56.000>
actor = 'facundobatista'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2003-06-30.13:34:25.000>
creator = 'dehex'
dependencies = []
files = []
hgrepos = []
issue_num = 763190
keywords = []
message_count = 5.0
messages = ['16737', '16738', '16739', '16740', '16741']
nosy_count = 3.0
nosy_names = ['nnorwitz', 'facundobatista', 'dehex']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue763190'
versions = ['Python 2.2']

[dehex]

Environment:
Python 2.2.2
win32all-150
Win2000 Server
Dell server
2 CPU Pentuim 4 emulating 4 CPU's.

Application:
Service with many (50-150) threads.

Problem:
The entire service exits unexepectedly with only a brief
reference made by Dr.Watson indicating the Windows
equivalent of SIGSEGV in RtlEnterCriticalSection.

Side info:
Known to have happened once, we believe it may have
happened three times in total but the two extra did not
leave even a Dr.Watson trace.

The known occurrence can be connected to our use of a
timer where the action routine restarts the timer.
The two extra's occurred at a point in time that connect
the problem event to the timer expiration.

The application have been used for five months,
runnning around the clock. The customer installation
currently use five instances of the base software, only
configuration differs.
It is arbitrary which instance fail.

We have no means to trigger the problem.

[nnorwitz]

Logged In: YES
user_id=33168

Are there any other C/Extension modules used which are not
from the standard python distribution? Can you make a self
contained test case?

I encourage you to test with 2.3 beta 2. There were some
thread changes which could affect this problem.

[dehex]

Logged In: YES
user_id=807857

Apart from what we initially reported, no extensions are used.
It is all pure Python and the only part of win32all used is the
support for running it as a service.

We are aware of the enhancements provided by 2.3 beta but
let it suffice to say that the customer is picky.

We have not been able to reproduce the problem in our test
environment, however the hardware is not as sophisticated.

[facundobatista]

Logged In: YES
user_id=752496

Please, could you verify if this problem persists in Python 2.3.4
or 2.4?

If yes, in which version? Can you provide a test case?

If the problem is solved, from which version?

Note that if you fail to answer in one month, I'll close this bug
as "Won't fix".

Thank you!

. Facundo

[facundobatista]

Logged In: YES
user_id=752496

Deprecated. Reopen only if still happens in 2.3 or newer.

. Facundo