Re: BUG #5682: Postgres Service crashes with exception 0xC0000135

On 09/29/2010 03:08 PM, Aswin J wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5682
> Logged by: Aswin J
> Email address: jayaswin(at)gmail(dot)com
> PostgreSQL version: 8.3.7
> Operating system: Windows

Windows ... what? XP? Vista? 7? 2003? 2008?
32- or 64-bit?

> 2010-09-27 10:33:30 IST LOG: server process (PID 22656) was terminated by
> exception 0xC0000135
> 2010-09-27 10:33:30 IST HINT: See C include file "ntstatus.h" for a
> description of the hexadecimal value.

"The application failed to initialize". Apparently usually due to
missing/bad runtime libraries, making this an odd thing to have arise
for a running Pg instance.

When does it crash? When forking a new backend (new connection) ? When
running a particular command? Randomly, when you're not doing anything?

> 2010-09-27 10:33:55 IST FATAL: the database system is in recovery mode
> 2010-09-27 10:33:55 IST LOG: all server processes terminated;
> reinitializing
> 2010-09-27 10:33:56 IST FATAL: pre-existing shared memory block is still in
> use
> 2010-09-27 10:33:56 IST HINT: Check if there are any old server processes
> still running, and terminate them.

There were some fixes to shared memory on windows since 8.3. Does 9.0
work better on your machine?

--
Craig Ringer