Hi all,
a strange error is happening to some of our customers.
They all have a Windows 10 installation on their machines with our
application and, of course, PostgreSQL 9.1 installed (migration to
9.5 upcoming in late summer/fall, but not applicable by now)
While working, suddenly PostgreSQL stops working, and log reports
2016-05-05 10:36:19 CEST LOG: server process (PID 5920) was
terminated by exception 0xC0000018
2016-05-05 10:36:19 CEST HINT: See C include file "ntstatus.h" for
a description of the hexadecimal value.
2016-05-05 10:36:19 CEST LOG: terminating any other active server
processes
2016-05-05 10:36:19 CEST WARNING: terminating connection because of
crash of another server process
2016-05-05 10:36:19 CEST DETAIL: The postmaster has commanded this
server process to roll back the current transaction and exit,
because another server process exited abnormally and possibly
corrupted shared memory.
2016-05-05 10:36:19 CEST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
[... above three lines repeated a bunch of times...]
2016-05-05 10:36:19 CEST LOG: all server processes terminated;
reinitializing
2016-05-05 10:36:29 CEST FATAL: pre-existing shared memory block is
still in use
2016-05-05 10:36:29 CEST HINT: Check if there are any old server
processes still running, and terminate them.
ntstatus.h refers to exception code as
0xC0000018
STATUS_CONFLICTING_ADDRESSES
{Conflicting Address Range} The specified address range
conflicts with the address space.
Googling I found many applications failing with that error and how
to fix them by setting a value in Registry, but these are not the
cases.
All I found in common of these machines (except Windows 10 and our
app :-) ) was ClassicShell. Uninstalling it seemed to resolve the
problem... until 2 hours ago, when one of them submitted us the same
crash with same error.
Trying to google deeper did not help for me.
This issue seems to be present on Windows 10 machines.
Any idea/thought/suggestion?
Thanks in advance,
Moreno.-