Re: BUG #6233: pg_dump hangs with Access Violation C0000005

From: "Pavel Holec" <holec(at)email(dot)cz>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6233: pg_dump hangs with Access Violation C0000005
Date: 2011-09-29 10:28:52
Message-ID: !&!AAAAAAAAAAAYAAAAAAAAAE8q5Jcv4mJImRanr8cGRrPCgAAAEAAAAMkKFO1ZvFtLt1i50HHyCNkBAAAAAA==@email.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 09/29/2011 05:18 AM, Holec wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6233
> Logged by: Holec
> Email address: holec(at)email(dot)cz
> PostgreSQL version: 8.4.8
> Operating system: Windows 7
> Description: pg_dump hangs with Access Violation C0000005
> Details:
>
> I use pg_dump on Windows 7 with:
> pg_dump -i -h 192.168.2.2 -p 5432 -U user -F c -b -v -f file.backup
> mydb

>>Does this crash happen when you back up a different database? Say, if you back up the `template1' database, does it crash then too?

>>Is this a 32-bit or 64-bit install of Windows 7? If 64-bit, are you using a 32-bit or 64-bit build of PostgreSQL?

>>Is there any antivirus software on the machine? If so, what type and version? Does the problem still happen if you turn it off and re-test?

>>--
>>Craig Ringer

My tests was on 4PC Win7 32bit and 2 PCs with Win 7 64bit and pg_dump 8.4.7 and 8.4.8 32bit. Behaviour is the same (everywhere the same db). Now I tested template1, my database without the data and new created database without the tables - the same result. Encoding I use 1250 because our system Win uses 1250 and UTF 8 made me problems with our letters with shapes. Next my test was create new database with UTF8 and backup - same result.

I tried Application Verifier from MS - output
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
- <avrf:logfile xmlns:avrf="Application Verifier">
- <avrf:logSession TimeStarted="2011-09-29 : 10:53:41" PID="3596" Version="2">
- <avrf:logEntry Time="2011-09-29 : 10:53:47" LayerName="Heaps" StopCode="0x6" Severity="Error">
<avrf:message>Corrupted heap pointer or using wrong heap.</avrf:message>
<avrf:parameter1>47a1000 - Heap handle used in the call.</avrf:parameter1>
<avrf:parameter2>6c2cf00 - Heap block involved in the operation.</avrf:parameter2>
<avrf:parameter3>100 - Size of the heap block.</avrf:parameter3>
<avrf:parameter4>3371000 - Heap where block was originally allocated.</avrf:parameter4>
- <avrf:stackTrace>
<avrf:trace>vrfcore!VerifierRegisterLayerEx+11b ( @ 0)</avrf:trace>
<avrf:trace>verifier!VerifierDisableFaultInjectionExclusionRange+3e65 ( @ 0)</avrf:trace>
<avrf:trace>verifier!VerifierDisableFaultInjectionExclusionRange+4131 ( @ 0)</avrf:trace>
<avrf:trace>verifier!VerifierDisableFaultInjectionExclusionRange+110a ( @ 0)</avrf:trace>
<avrf:trace>verifier!VerifierDisableFaultInjectionExclusionRange+12f0 ( @ 0)</avrf:trace>
<avrf:trace>verifier!VerifierDisableFaultInjectionExclusionRange+3130 ( @ 0)</avrf:trace>
<avrf:trace>ntdll!RtlpNtMakeTemporaryKey+48b5 ( @ 0)</avrf:trace>
<avrf:trace>ntdll!EtwSetMark+e743 ( @ 0)</avrf:trace>
<avrf:trace>ntdll!wcsnicmp+caa ( @ 0)</avrf:trace>
<avrf:trace>vfbasics!+6cf3fe9c ( @ 0)</avrf:trace>
<avrf:trace>kernel32!HeapFree+14 ( @ 0)</avrf:trace>
<avrf:trace>vfbasics!+6cf41024 ( @ 0)</avrf:trace>
<avrf:trace>MSVCR80!free+cd ( @ 0)</avrf:trace>
</avrf:stackTrace>
</avrf:logEntry>
</avrf:logSession>
</avrf:logfile>

McAfee Security centr uninstalled...

If it can helps I attach mydb without data.

Pavel holec

Attachment Content-Type Size
emptydb.zip application/x-zip-compressed 17.1 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Yaamini Bist 2011-09-29 11:23:08 PostGre compatible to RHEL 6.1
Previous Message Kyotaro HORIGUCHI 2011-09-29 10:24:26 Re: [v9.2] make_greater_string() does not return a string in some cases