Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Jan 2009 16:30:04 +0100
From:      "Alexey Shuvaev" <shuvaev@physik.uni-wuerzburg.de>
To:        Arthur Melo <arthur@afabrica.net>
Cc:        gnome@freebsd.org, freebsd-ports@freebsd.org
Subject:   Re: (no subject)
Message-ID:  <20090127153004.GA14427@wep4035.physik.uni-wuerzburg.de>
In-Reply-To: <201435c80901261158g45e9bb41tcd9211cdaa534483@mail.gmail.com>
References:  <201435c80901261158g45e9bb41tcd9211cdaa534483@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 26, 2009 at 04:58:23PM -0300, Arthur Melo wrote:
> Dear Srs.
> 
> The error ocurred when I enter in my gmail.
> 
> [suporte@bsdteste /usr/home/suporte]$ firefox --sync
> :1: error: unexpected character `\1', expected keyword - e.g. `style'
> NP_Initialize
> New
> open dsp: No such file or directory
> SetWindow
> SetWindow
> NewStream
> WriteReady
> Write
> decoding...
> shmget: Cannot allocate memory
  ^^^^^^^
> Size = 547 x 225
> shmat: Invalid argument
> The program 'firefox-bin' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAccess (attempt to access private resource denied)'.
>   (Details: serial 33 error_code 10 request_code 146 minor_code 1)
>   (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.)
> [suporte@bsdteste /usr/home/suporte]$ uname -a
> FreeBSD bsdteste.grupoatemde.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE
> #0: Thu Jan  1 14:37:25 UTC 2009
> root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
> [suporte@bsdteste /usr/home/suporte]$
> 
Any chance you have running postgresql server on this machine?
Seems you are running out of kernel's limits on SysV shared memory resources.
You could try doing what is in postgresql's pkg-message:

[snip]
To allow many simultaneous connections to your PostgreSQL server, you
should raise the SystemV shared memory limits in your kernel. Here are
example values for allowing up to 180 clients (configurations in
postgresql.conf also needed, of course):
  options         SYSVSHM
  options         SYSVSEM
  options         SYSVMSG
  options         SHMMAXPGS=65536
  options         SEMMNI=40
  options         SEMMNS=240
  options         SEMUME=40
  options         SEMMNU=120
[snip]

My 0.02$,
Alexey.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090127153004.GA14427>