Dhanaraj M

pgAdmin3 - Failed to start (BadAlloc problem)

Recently I heard from the customer that pgadmin fails to start with the information..

     BadAlloc (insufficient resources for operation)

	(Details: serial 172 error_code 11 request_code 131 minor_code 5)
	(Note to programmers: normally, X errors are reported asynchronously;
	 that is, you will receive the error a while after causing it.
	 To debug your program, run it with the --sync command line
	 option to change this behavior. You can then get a meaningful
	 backtrace from your debugger if you break on the gdk_x_error() function.)

I root-caused the problem. The summary is here..

There has been a Xserver fix integrated which affects both Xsun/Xorg (sprac/x86). It was integrated into SNV_79a & S10U5-05.
Hence, 119050-36 (sparc) & 119060-35 (x86) bad patches cause the Badalloc problem.

This is fixed in SNV_84 & S10U5-09. Another solution is to upgrade to the recent 119059-40 (sparc) & 119060-40 (x86) patch level or the above.

Another workaround for X86:

1. To work around the described issues for the Xorg(1) server, the affected X Server extensions may be disabled.

    $ /usr/X11/bin/Xorg -extension MIT-SHM

2. The X Server extensions may also be disabled by editing the xorg.conf(4) file. For example, to disable the MIT-SHM extension, the following lines may be added to the xorg.conf(4) file:

    Section "Extensions" Option "MIT-SHM" "disable"  EndSection

Posted at 11:37AM Feb 15, 2008 by dhanarajm in Sun  |  Comments[3]