Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 0F0E91337BFE for ; Tue, 10 May 2011 09:36:31 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 45292-02-4 for ; Tue, 10 May 2011 12:36:23 +0000 (UTC) X-Greylist: delayed 00:15:14.887517 by SQLgrey-1.7.6 Received: from outboundmta02.oricom.ca (outboundmta02.oricom.ca [64.18.160.77]) by mail.postgresql.org (Postfix) with ESMTP id 0F9301337C18 for ; Tue, 10 May 2011 09:35:55 -0300 (ADT) X-ASG-Debug-ID: 1305030038-24aab8840001-ovxuox Received: from Gateway (static-dslcom3-026.express.oricom.ca [64.18.178.26]) by outboundmta02.oricom.ca with ESMTP id 3jPuLT9YFywK7sms; Tue, 10 May 2011 08:20:38 -0400 (EDT) X-Barracuda-Envelope-From: mark.watson@jurisconcept.ca X-Barracuda-Apparent-Source-IP: 64.18.178.26 From: "Mark Watson" To: "'Greg Smith'" Cc: References: <4DC85DF3.9030105@agliodbs.com> <4DC86132.20604@agliodbs.com> <4DC87067.4050101@2ndQuadrant.com> <4DC88CFF.9020301@2ndquadrant.com> In-Reply-To: <4DC88CFF.9020301@2ndquadrant.com> Subject: Re: 9.1Beta1 - Repeatable Crash on Windows Date: Tue, 10 May 2011 08:15:30 -0400 X-ASG-Orig-Subj: RE: [TESTERS] 9.1Beta1 - Repeatable Crash on Windows Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcwOrQOi5vef3URzRKCyK/lUPYxD/wAXOeww X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18417 X-Barracuda-Connect: static-dslcom3-026.express.oricom.ca[64.18.178.26] X-Barracuda-Start-Time: 1305030038 X-Barracuda-URL: http://64.18.160.77:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at oricom.ca X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.63323 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.8 tagged_above=-10 required=5 tests=BAYES_50=0.8 X-Spam-Level: X-Archive-Number: 201105/9 X-Sequence-Number: 228 -----Message d'origine----- De : pgsql-testers-owner@postgresql.org = [mailto:pgsql-testers-owner@postgresql.org] De la part de Greg Smith Envoy=C3=A9 : 9 mai 2011 20:55 =C3=80 : Richard Broersma Cc : pgsql-testers@postgresql.org Objet : Re: [TESTERS] 9.1Beta1 - Repeatable Crash on Windows Richard Broersma wrote: > Here is what the logs show: > > 2011-05-09 07:49:37 PDT LOG: server process (PID 2848) was terminated > by exception 0xC0000005 > =20 Too bad, that's just a generic "accessed memory you shouldn't have"=20 exception. Not much help narrowing down the source. That could be a=20 driver or hardware issue, but since you say it's repeatable that seems=20 less likely. At this point, fork in the road. If someone else can reproduce this on=20 another Windows system, they may be able to run with it. But if you can = spare some time to dig further, the instructions at=20 http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_Postgr= eSQL_backend_on_Windows=20 go over how to trace into where it's actually failing at yourself. If=20 you run PostgreSQL on Windows, that's good defensive practice to fit in=20 on a day it's not an emergency to do so. (The same is true of any=20 platform, it just takes more time to setup on Windows) ------------------------ I can reproduce the same exception in another manner. I tried to get a = stack trace but cannot seem to attach to the process using either = process explorer or WinDBG. I reproduced this using the current beta = pgAdmin by right-clicking on Login Roles, select New login role, Role = name test, password testp, and selecting all role privliges then OK. The = service crashes. PID 5432 below is the pgAdmin process. My log file (sorry about the French): 2011-05-10 08:00:26 EDT LOG: processus serveur (PID 5432) a = =C3=A9t=C3=A9 arr=C3=AAt=C3=A9 par l'exception 0xC0000005 2011-05-10 08:00:26 EDT ASTUCE : Voir le fichier d'en-t=C3=AAte C = =C2=AB ntstatus.h =C2=BB pour une description de la valeur hexad=C3=A9cimale. 2011-05-10 08:00:26 EDT LOG: arr=C3=AAt des autres processus serveur = actifs 2011-05-10 08:00:26 EDT ATTENTION: arr=C3=83=C2=AAt de la connexion = =C3=83 cause de l'arr=C3=83=C2=AAt brutal d'un autre processus serveur 2011-05-10 08:00:26 EDT D=C3=83=E2=80=B0TAIL: Le postmaster a = command=C3=83=C2=A9 =C3=83 ce processus serveur d'annuler la = transaction courante et de quitter car un autre processus serveur a = quitt=C3=83=C2=A9 anormalement et qu'il existe probablement de la m=C3=83=C2=A9moire = partag=C3=83=C2=A9e corrompue. 2011-05-10 08:00:26 EDT ASTUCE : Dans un moment, vous devriez = =C3=83=C2=AAtre capable de vous reconnecter =C3=83 la base de donn=C3=83=C2=A9es et de relancer votre commande. 2011-05-10 08:00:26 EDT ATTENTION: arr=C3=AAt de la connexion =C3=A0 = cause de l'arr=C3=AAt brutal d'un autre processus serveur 2011-05-10 08:00:26 EDT D=C3=89TAIL: Le postmaster a command=C3=A9 = =C3=A0 ce processus serveur d'annuler la transaction courante et de quitter car un autre processus serveur a quitt=C3=A9 = anormalement et qu'il existe probablement de la m=C3=A9moire partag=C3=A9e = corrompue. 2011-05-10 08:00:26 EDT ASTUCE : Dans un moment, vous devriez =C3=AAtre = capable de vous reconnecter =C3=A0 la base de donn=C3=A9es et de relancer votre commande. 2011-05-10 08:00:26 EDT LOG: tous les processus serveur se sont = arr=C3=AAt=C3=A9s, r=C3=A9initialisation 2011-05-10 08:00:36 EDT FATAL: le bloc de m=C3=A9moire partag=C3=A9 = pr=C3=A9-existant est toujours en cours d'utilisation 2011-05-10 08:00:36 EDT ASTUCE : V=C3=A9rifier s'il n'y a pas de vieux = processus serveur en cours d'ex=C3=A9cution. Si c'est le cas, fermez-les. - Mark Watson