Re: pgAdmin 4 crash on startup
Hi Sandeep, Thank you for your assistance with this. The virtual machine has 6.00 GB of memory. At the time the issue occurs, 4.7 GB is shown as in use, 1,858 MB as available, with 1,395 MB in use as system cache. If I attach Visual Studio 2010 to the process as it is starting, it starts up without any errors, although the text rendering is very difficult to read. (See the screenshot at https://www.dropbox.com/s/lmlhak0t2238ern/Screen%20Shot%202017-11-30%20at%2009.42.21.png?dl=0) If I let it start without Visual Studio 2010 attached, it still access violates. You can see a screenshot of the UI at the time of the access violation at https://www.dropbox.com/s/j8kndstmr8647k9/Screen%20Shot%202017-11-30%20at%2009.39.13.png?dl=0 Attaching the debugger once the access violation has occurred, I get the following details: Unhandled exception at 0x61efbe7f in pgAdmin4.exe: 0xC005: Access violation reading location 0x0bf88000. You can get a mini dump file generated by Visual Studio from here: https://www.dropbox.com/s/kxg3qkmyci6vais/pgAdmin4.7z?dl=0 The disassembly around the access violation looks like this: 61EFBE68 cmpedi,6 61EFBE6B jbe61EFBEB5 61EFBE6D leaedi,[ecx+ebx] 61EFBE70 pxor xmm1, xmm1 61EFBE74 leaebx,[eax+ebx*4] 61EFBE77 movdword ptr [esp],eax 61EFBE7A xoreax,eax 61EFBE7C leaedi,[edx+edi*2] > 61EFBE7F movdqu xmm0,xmmword ptr [edi] 61EFBE83 addeax,1 61EFBE86 addedi,10h 61EFBE89 addebx,20h 61EFBE8C movdqa xmm2,xmm0 61EFBE90 punpckhwd xmm0,xmm1 61EFBE94 punpckhwd xmm2,xmm1 61EFBE98 movaps xmmword ptr [ebx-10h],xmm0 61EFBE9C movaps xmmword ptr [ebx-20h],xmm2 61EFBEA0 cmpdword ptr [esp+0Ch],eax 61EFBEA4 ja 61EFBE7F 61EFBEA6 movebx,dword ptr [esp+4] 61EFBEAA moveax,dword ptr [esp] 61EFBEAD addpsi,ebx 61EFBEAF cmpdword ptr [esp+8],ebx 61EFBEB3 je 61EFBEF32 61EFBEB5 leaedi,[ecx+esi] 61EFBEB8 leaebx,[esi*4] 61EFBEBF movzx edi,word ptr [edx+edi*2] 61EFBEC3 movdword ptr [eax+esi*4],edi 61EFBEC6 leaedi,[esi+1] The current register contents are: EAX = 0039 EBX = 00278920 ECX = 01D3 EDX = 0BF878BC ESI = EDI = 0BF87FF2 EIP = 61EFBE7F ESP = 002781C0 EBP = 002781E8 EFL = 00010206 The contents of the memory at 0x0bf88000 are not viewable in the debugger. The contents of the memory at 0x0bf87ff2 are: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?? ?? ?? ... The contents of the memory at 0x0bf878bc are ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ... The contents of the memory at 0x002781C0 are: 0x002781C000 82 27 00 e0 01 00 00 e6 01 00 00 3c 00 00 00 45 29 00 000x002781D445 29 00 00 45 29 00 00 e0 00 00 00 e6 01 00 00 e0 a2 27 000x002781E804 00 00 00 a7 83 b4 61 e6 01 00 00 30 0f 00 00 40 c4 f8 610x002781FCb9 03 00 00 7d ef 00 00 7d ef 00 00 7d ef 00 00 7d ef 00 00... ... 0x002786B07d ef 00 00 7d ef 00 00 7d ef 00 00 7d ef 00 00 7d ef 00 000x002786C45d ef 00 00 fb de 00 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 Thanks again for your assistance. Kind regards, Gareth Marshall On Tue, 28 Nov 2017, at 20:49, Sandeep Thakkar wrote: > > > On Tue, Nov 28, 2017 at 2:28 PM, Dave Page wrote:>> > Sandeep, can you help try to figure this out please? >> > Sure Dave. > >> On Tue, Nov 28, 2017 at 4:52 AM, Gareth Marshall >> wrote:>>> Hi >>> > Hi Gareth, > >>> I'm having an issue with pgAdmin 4 crashing on startup. Any >>> assistance>>> in getting it working would be very much appreciated. >>> >>> == pgAdmin Version == >>> It is the version of pgAdmin 4 installed by the EnterpriseDB >>> PostgreSQL>>> 10.1-2-windows-x64 installer. The file properties for the >>> executable say>>> it is version 2.0.0.0. >>> >>> == Configure Options == >>> Unknown. I am using binaries from the EnterpriseDB installer. >>> >>> == Operating System == >>> I'm running on Windows 7 Ultimate (Build 7601: Service Pack 1) >>> 64-bit,>>> and I am connected to it over a remote desktop connection. >>> >>> == Server or Desktop Mode == >>> I am starting it from the Windows start menu as installed by the >>> installer. I assume that this would be desktop mode. >>> >>> == Qt Version == >>> The properties of QtGui.dll say it is version 5.9.1.0. >>> >>> == Python Version == >>> The properties of python27.dll say it is version 2.7.11150.1013. >>> I also>>> have Python 2.7.12 in my Windows path. >>> >>> == pip freeze == >>> C:\Program Files\PostgreSQL\10\pgAdmin 4\bin>pip freeze >>> Pygments==2.2.0 >>> >>> == Steps to Reproduce == >>> I launch pgAdmin 4 by clicking on the shortcut in the start menu >>> created>>> by the installer, or by double clicking on the executable in >>> c:\Program>>> Files\PostgreSQL\10\pgAdmin 4\bin. >>> >>> The application runs for a while, and paints some UI: I can see >>>
Re: pgAdmin 4 crash on startup
Hi Sandeep,
After the successful startup of pgAdmin 4 with the debugger attached,
I connected to my servers and tested some other functionality without
any issues.
Since doing that, starting pgAdmin 4 without the debugger is also
starting ok. The text rendering still isn't great, but it doesn't crash,
and appears to be functioning as would be expected.
This makes me suspect that either there is some configuration
information that has now been saved that is preventing the problem from
occurring again or that the problem only happens if some uninitialised
memory is accessed, and that previously I was unlucky to have it cause
problems but now am avoiding hitting bad values for that memory.
Kind regards,
Gareth
On Tue, 28 Nov 2017, at 20:49, Sandeep Thakkar wrote:
>
>
> On Tue, Nov 28, 2017 at 2:28 PM, Dave Page wrote:>>
> Sandeep, can you help try to figure this out please?
>>
> Sure Dave.
>
>> On Tue, Nov 28, 2017 at 4:52 AM, Gareth Marshall
>> wrote:>>> Hi
>>>
> Hi Gareth,
>
>>> I'm having an issue with pgAdmin 4 crashing on startup. Any
>>> assistance>>> in getting it working would be very much appreciated.
>>>
>>> == pgAdmin Version ==
>>> It is the version of pgAdmin 4 installed by the EnterpriseDB
>>> PostgreSQL>>> 10.1-2-windows-x64 installer. The file properties for the
>>> executable say>>> it is version 2.0.0.0.
>>>
>>> == Configure Options ==
>>> Unknown. I am using binaries from the EnterpriseDB installer.
>>>
>>> == Operating System ==
>>> I'm running on Windows 7 Ultimate (Build 7601: Service Pack 1)
>>> 64-bit,>>> and I am connected to it over a remote desktop connection.
>>>
>>> == Server or Desktop Mode ==
>>> I am starting it from the Windows start menu as installed by the
>>> installer. I assume that this would be desktop mode.
>>>
>>> == Qt Version ==
>>> The properties of QtGui.dll say it is version 5.9.1.0.
>>>
>>> == Python Version ==
>>> The properties of python27.dll say it is version 2.7.11150.1013.
>>> I also>>> have Python 2.7.12 in my Windows path.
>>>
>>> == pip freeze ==
>>> C:\Program Files\PostgreSQL\10\pgAdmin 4\bin>pip freeze
>>> Pygments==2.2.0
>>>
>>> == Steps to Reproduce ==
>>> I launch pgAdmin 4 by clicking on the shortcut in the start menu
>>> created>>> by the installer, or by double clicking on the executable in
>>> c:\Program>>> Files\PostgreSQL\10\pgAdmin 4\bin.
>>>
>>> The application runs for a while, and paints some UI: I can see
>>> a menu>>> bar with options File, Object, Tools, and Help. Below that on
>>> the left>>> is a pane titled Browser. To the right is a pane with a
>>> Dashboard pane>>> active. There are also Properties, SQL, Statistics, and
>>> Dependencies>>> tabs, as well as navigation arrows and a close button.
>>>
>>> Once this UI appears, Windows displays a message saying "pgAdmin 4>>>
>>> Desktop Runtime has stopped working". The problem details are:
>>>
>>> Problem Event Name: APPCRASH
>>> Application Name: pgAdmin4.exe
>>> Application Version: 2.0.0.0
>>> Application Timestamp: 5a030f94
>>> Fault Module Name: Qt5Gui.dll
>>> Fault Module Timestamp: 59539955
>>> Exception Code: c005
>>> Exception Offset: 003bbe7f
>>> OS Version: 6.1.7601.2.1.0.256.1
>>> Locale ID: 3081
>>> Additional Information 1: 0a9e
>>> Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
>>> Additional Information 3: 0a9e
>>> Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
>>>
>>> I believe that this error code corresponds to an Access
>>> Violation in>>> Qt5Gui.dll.
>>>
> Yes, Exception code: c005 corresponds to an Access Violation which
> probably means application tried to access unallocated memory. Did you
> try debugging it with Microsoft Visual Studio? Could you also share
> the total RAM on this VM?>
>>> The details for my Display are:
>>> Name: Microsoft Virtual Machine Bus Video Device
>>> PNP Device ID:
>>> VMBUS\{5620E0C7-8062-4DCE-AEB7-
>>> 520C7EF76171}\5&296C0F0E&0&{5620E0C7-8062-4DCE-AEB7-520C7EF76171}>>>
>>> Adapter Type: Not Available, Microsoft compatible
>>> Adapter Description: Microsoft Virtual Machine Bus Video Device
>>> Adapter RAM: Not Available
>>> Installed Drivers: VMBusVideoD.dll
>>> Driver Version: 6.1.7601.17514
>>> INF File: wvmbusvideo.inf (SynthVid section)
>>> Color Planes: Not Available
>>> Color Table Entries: Not Available
>>> Resolution: Not Available
>>> Bits/Pixel: Not Available
>>> Memory Address: 0xFFB0-0xFFEF
>>> Driver: c:\windows\system32\drivers\vmbusvideom.sys
>>> (6.1.7601.17514,>>> 22.00 KB (22,528 bytes), 2011-05-20 12:34)
>>>
>>> The Virtual Machine is running under Hyper-V on Windows 2008 R2.
>>>
>>> Kind regards,
>>> Gareth Marshall
>>>
>>
>>
>>
>> --
>> Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com The Enterprise
>> PostgreSQL Company>>
>
>
>
> --
> Sandeep Thakkar
> EnterpriseDB: http://www.enterpr
Re: 500 Internal Server Error
Dear Ben! What is the solution of this problem? I don't have account there. :-( Thank you! BW dd 2017-11-22 21:29 GMT+01:00 Ben Nachtrieb : > Never mind. Found the bug #: Bug #2806 > > Found here: https://redmine.postgresql.org/issues/2806 > > Ben Nachtrieb |(303) 350-4287 > > Only accredited investors and qualified clients will be admitted as > limited partners to a Crescat fund. For natural persons, investors must > meet SEC requirements including minimum annual income or net worth > thresholds. Crescat funds are being offered in reliance on an exemption > from the registration requirements of the Securities Act of 1933 and are > not required to comply with specific disclosure requirements that apply to > registration under the Securities Act. The SEC has not passed upon the > merits of or given its approval to the Crescat funds, the terms of the > offering, or the accuracy or completeness of any offering materials. A > registration statement has not been filed for any Crescat fund with the > SEC. Limited partner interests in the Crescat funds are subject to legal > restrictions on transfer and resale. Investors should not assume they will > be able to resell their securities. Investing in securities involves risk. > Investors should be able to bear the loss of their investment. Investments > in the Crescat funds are not subject to the protections of the Investment > Company Act of 1940. Performance data represents past performance, and past > performance does not guarantee future results. Performance data is subject > to revision following each monthly reconciliation and annual audit. Current > performance may be lower or higher than the performance data presented. > Crescat is not required by law to follow any standard methodology when > calculating and representing performance data. The performance of Crescat > funds may not be directly comparable to the performance of other private or > registered funds. Investors may obtain the most current performance data > and private offering memorandum for a Crescat fund by contacting Linda > Smith at (303) 271-9997 or by sending a request via email to > lsm...@crescat.net. See the private offering memorandum for each Crescat > fund for complete information and risk factors. > > > > *From:* Ben Nachtrieb > *Sent:* Wednesday, November 22, 2017 12:32 PM > *To:* pgadmin-support@lists.postgresql.org > *Cc:* Ben Nachtrieb > *Subject:* 500 Internal Server Error > > > > Hello, > > > > When I send a query, unexpectedly and seemingly randomly I get the > following text in the Message tab for the query tool output: > > > > “ 500 > Internal Server Error Internal Server Error The server > encountered an internal error and was unable to complete your request. > Either the server is overloaded or there is an error in the > application.” > > > > Notes: > > -The html is part of the message. > > -It doesn’t seem to matter what query is sent. > > -The actual query seems to stay active (as if it is still working), but > eventually comes back with a wait event: ClientWrite. > > -We can remedy the situation by closing the query tool window (hence > closing the session) and opening a new query too window (whilst never > closing pgAdmin 4 or the connection to the server) then sending the query > again. > > -We are connected to a Linux VM via my Windows 7 PC. > > -This happens probably 10 times a day while queries are being developed > and tested. > > > > I have: > > > > *Version* > > 2.0 > > *Copyright* > > Copyright 2013 - 2017, The pgAdmin Development Team > > *Python Version* > > 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit > (Intel)] > > *Flask Version* > > 0.12.2 > > *Application Mode* > > Desktop > > *Current User* > > pgadm...@pgadmin.org > > > > What is causing this? What is the fix? Is this a bug? I see similar bugs > listed, but they all seem to depend on a certain type of query (I think). > > > > Thanks! > > > > *Ben * > > >
