Re: Chromium Crashes
Hello, On 10-Jun-2012, at 11:40 AM, The Todds wrote: > Yes this is the latest build (5th June) of Chromium. I suppose I could > revert to the 18.0.1025.168 version using portdowngrade until this > fault is fixed. > > Glenn It looks like the port is lagging back from mainstream. You could also write to the maintainers. I am copying the maintainers just in case someone is already on it. Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 > On Sun, 2012-06-10 at 10:37 +0530, Subhro Sankha Kar wrote: >> Hello, >> >> It looks like you have hit a documented bug. See this: >> >> http://code.google.com/p/chromium/issues/detail?id=125447 >> http://src.chromium.org/viewvc/chrome?view=rev&revision=141116 >> >> Did you try upgrading your ports? >> >> Thanks >> Subhro >> >> -- >> Subhro Sankha Kar >> System Administrator >> Working and Playing with FreeBSD since 2002 >> >> On 10-Jun-2012, at 10:11 AM, The Todds wrote: >> >>> I have just have built and installed Chromium 19.0.1084.52 from the >>> ports on my amd64 machine - 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Nov 5 >>> 08:40:03 NZDT 2011 >>> >>> Portversion chromium-19.0.1084.52_2 = up-to-date with port >>> >>> On web sites which contains graphics Chromium crashes with the following >>> error: >>> >>> [3152:171983296:14310963010:ERROR:CONSOLE(1)] "Uncaught ReferenceError: >>> ntp is not defined", source: (1) >>> >>> Any ideas how to resolve this issue. >>> >>> Glenn >>> >>> >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >> >> > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Chromium Crashes
Yes this is the latest build (5th June) of Chromium. I suppose I could revert to the 18.0.1025.168 version using portdowngrade until this fault is fixed. Glenn On Sun, 2012-06-10 at 10:37 +0530, Subhro Sankha Kar wrote: > Hello, > > It looks like you have hit a documented bug. See this: > > http://code.google.com/p/chromium/issues/detail?id=125447 > http://src.chromium.org/viewvc/chrome?view=rev&revision=141116 > > Did you try upgrading your ports? > > Thanks > Subhro > > -- > Subhro Sankha Kar > System Administrator > Working and Playing with FreeBSD since 2002 > > On 10-Jun-2012, at 10:11 AM, The Todds wrote: > > > I have just have built and installed Chromium 19.0.1084.52 from the > > ports on my amd64 machine - 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Nov 5 > > 08:40:03 NZDT 2011 > > > > Portversion chromium-19.0.1084.52_2 = up-to-date with port > > > > On web sites which contains graphics Chromium crashes with the following > > error: > > > > [3152:171983296:14310963010:ERROR:CONSOLE(1)] "Uncaught ReferenceError: > > ntp is not defined", source: (1) > > > > Any ideas how to resolve this issue. > > > > Glenn > > > > > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Chromium Crashes
Hello, It looks like you have hit a documented bug. See this: http://code.google.com/p/chromium/issues/detail?id=125447 http://src.chromium.org/viewvc/chrome?view=rev&revision=141116 Did you try upgrading your ports? Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 On 10-Jun-2012, at 10:11 AM, The Todds wrote: > I have just have built and installed Chromium 19.0.1084.52 from the > ports on my amd64 machine - 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Nov 5 > 08:40:03 NZDT 2011 > > Portversion chromium-19.0.1084.52_2 = up-to-date with port > > On web sites which contains graphics Chromium crashes with the following > error: > > [3152:171983296:14310963010:ERROR:CONSOLE(1)] "Uncaught ReferenceError: > ntp is not defined", source: (1) > > Any ideas how to resolve this issue. > > Glenn > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Chromium Crashes
I have just have built and installed Chromium 19.0.1084.52 from the ports on my amd64 machine - 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Nov 5 08:40:03 NZDT 2011 Portversion chromium-19.0.1084.52_2 = up-to-date with port On web sites which contains graphics Chromium crashes with the following error: [3152:171983296:14310963010:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source: (1) Any ideas how to resolve this issue. Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: chromium crashes
On Mon, Oct 18, 2010 at 11:30:28AM -0700, Chip Camden wrote: > Quoth Chad Perrin on Monday, 18 October 2010: > > The problem I'm having is that I can't get a vi-like keybindings > > extension to work. I guess it's likely that most extensions haven't been > > tested for compatibility on FreeBSD, though. > > Are you trying vimperator, or some other extension? Oops. I appear to have accidentally replied directly to Chip instead of to the list. Basically, I said: I don't think there's a vimperator for Chrome. I have tried both YakShave and Vimium, however, and neither worked. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpKDRswZ1MTl.pgp Description: PGP signature
Re: chromium crashes
Quoth Chad Perrin on Monday, 18 October 2010: > The problem I'm having is that I can't get a vi-like keybindings > extension to work. I guess it's likely that most extensions haven't been > tested for compatibility on FreeBSD, though. > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Hey Chad, Are you trying vimperator, or some other extension? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpT3aNjWjK8Y.pgp Description: PGP signature
Re: chromium crashes
The problem I'm having is that I can't get a vi-like keybindings extension to work. I guess it's likely that most extensions haven't been tested for compatibility on FreeBSD, though. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpWKTWQ98yQ3.pgp Description: PGP signature
Re: chromium crashes
On Sat, 16 Oct 2010, Marco Beishuizen wrote: Hi, I tried to run chromium as browser today but it crashes immediately: ... [1016/211130:WARNING:base/debug_util_posix.cc(228)] Don't know how to do this The program 'chrome' 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 741 error_code 10 request_code 139 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.) ... Has anyone else has this too? Thanks in advance. Regards, Marco It seems that I had to reboot first in order to run Chromium. Strange that rebooting is required. Thanks for the answers though. Regards, Marco -- A bureaucrat's idea of cleaning up his files is to make a copy of everything before he destroys it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: chromium crashes
Marco Beishuizen writes: > Hi, > > I tried to run chromium as browser today but it crashes immediately: > > ... > [1016/211130:WARNING:base/debug_util_posix.cc(228)] Don't know how to > do this > The program 'chrome' 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 741 error_code 10 request_code 139 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.) > ma...@yokozuna:~% opera > opera [crash logging]: Can't read kernel memory: : /dev/mem: > Permission denied > opera [crash logging]: CRASH!! > got signal SIGSEGV at address 298C9B5D > ... > > Has anyone else has this too? > Thanks in advance. > Regards, > Marco Chrome runs without errors on my desktop (8.1-RELEASE i386). There is only one message at the start time. // [1017/150910:WARNING:base/debug_util_posix.cc(228)] Don't know how to do this // Sincerely, -- 소여물 황병희(黃炳熙) | .. 출항 15분전.. "I wanta see more of the kids too. I want to settle down a little bit." -- Johnny Fontane, "Chapter 12", page 161 pgpwusWXXuMeH.pgp Description: PGP signature
Re: chromium crashes
Quoth Marco Beishuizen on Saturday, 16 October 2010: > Hi, > > I tried to run chromium as browser today but it crashes immediately: > > ... > [1016/211130:WARNING:base/debug_util_posix.cc(228)] Don't know how to do > this > The program 'chrome' 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 741 error_code 10 request_code 139 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.) > ma...@yokozuna:~% opera > opera [crash logging]: Can't read kernel memory: : /dev/mem: Permission > denied > opera [crash logging]: CRASH!! > got signal SIGSEGV at address 298C9B5D > ... > > Has anyone else has this too? > Thanks in advance. > Regards, > Marco > > -- > He who has imagination without learning has wings but no feet. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I'm running chromium fine on 8.1-STABLE amd64 It does give the "Don't know how to do this" warning, but then proceeds OK. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgprQCuR07Lyc.pgp Description: PGP signature
chromium crashes
Hi, I tried to run chromium as browser today but it crashes immediately: ... [1016/211130:WARNING:base/debug_util_posix.cc(228)] Don't know how to do this The program 'chrome' 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 741 error_code 10 request_code 139 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.) ma...@yokozuna:~% opera opera [crash logging]: Can't read kernel memory: : /dev/mem: Permission denied opera [crash logging]: CRASH!! got signal SIGSEGV at address 298C9B5D ... Has anyone else has this too? Thanks in advance. Regards, Marco -- He who has imagination without learning has wings but no feet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
