Re: Chrome crashing system (amd64-10.0-CURRENT)
In message 20120517071141.gl2...@thinkbsd.divinix.org, John Hixson writes: On Thu, May 17, 2012 at 01:15:54AM -0500, Conrad J. Sabatier wrote: For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To make matters worse, no trace of what's happening is anywhere to be found. Nothing in any log files. The system doesn't drop into the kernel debugger, either. It's either a hard freeze or sudden reboot. I've tried rebuilding the chromium port, with both clang and gcc 4.6, to no avail. I've also updated the system sources several times this week and remade world/kernel. Nothing seems to help. I'm totally stumped as to how to determine what's going on here. Any suggestions as to how to obtain some useful info? To add to this, I've had the same problem on 10-CURRENT for several months now. I think we're dealing with two issues here. First, the application is passing out of bound data or corrupt data to the O/S. Secondly, FreeBSD should be able to withstand this (DoS). -- Cheers, Cy Schubert cy.schub...@komquats.com FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On Thu, May 17, 2012 at 04:12:15PM -0700, Evan Martin wrote: On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier conr...@cox.net wrote: Thanks. I tried those, and it still locked up. I finally just moved away ~/.config/chromium, and it started up OK. Luckily, I was able to restore pretty much everything from my synced data. It's a little surprising to me that a userspace app is able to nuke your system, but perhaps the bug is just something mundane like out of control memory allocations and it's just swapping. I just discovered while poking around again under ~/.config that my old chromium directory (that is, the directory file itself) had somehow become corrupted. This was most likely what was causing chrome to go berserk before. I'm using SU+J here, and this problem wasn't detected by fsck before. I only discovered it this evening when, after having already deleted all of the files in the directory, rmdir failed with the error message Directory not empty. After booting single-user and running fsck twice (to force it not to use the journal), looks like everything's back to normal now. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Chrome crashing system (amd64-10.0-CURRENT)
For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To make matters worse, no trace of what's happening is anywhere to be found. Nothing in any log files. The system doesn't drop into the kernel debugger, either. It's either a hard freeze or sudden reboot. I've tried rebuilding the chromium port, with both clang and gcc 4.6, to no avail. I've also updated the system sources several times this week and remade world/kernel. Nothing seems to help. I'm totally stumped as to how to determine what's going on here. Any suggestions as to how to obtain some useful info? Thanks! -- Conrad J. Sabatier conr...@cox.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On Thu, May 17, 2012 at 01:15:54AM -0500, Conrad J. Sabatier wrote: For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To make matters worse, no trace of what's happening is anywhere to be found. Nothing in any log files. The system doesn't drop into the kernel debugger, either. It's either a hard freeze or sudden reboot. I've tried rebuilding the chromium port, with both clang and gcc 4.6, to no avail. I've also updated the system sources several times this week and remade world/kernel. Nothing seems to help. I'm totally stumped as to how to determine what's going on here. Any suggestions as to how to obtain some useful info? To add to this, I've had the same problem on 10-CURRENT for several months now. -John ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On 5/17/2012 2:11 AM, John Hixson wrote: On Thu, May 17, 2012 at 01:15:54AM -0500, Conrad J. Sabatier wrote: For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To add to this, I've had the same problem on 10-CURRENT for several months now. Are you guys building ports with clang? There's a known bug with google-perftools, when it's built with clang, chrome will crash upon launch. chrome itself can be built with any compiler, but if google-perftools is built with clang, crash! http://code.google.com/p/gperftools/issues/detail?id=394 -- Chuck Burns ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On 2012-05-17 14:20, Chuck Burns wrote: On 5/17/2012 2:11 AM, John Hixson wrote: On Thu, May 17, 2012 at 01:15:54AM -0500, Conrad J. Sabatier wrote: For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To add to this, I've had the same problem on 10-CURRENT for several months now. Are you guys building ports with clang? There's a known bug with google-perftools, when it's built with clang, chrome will crash upon launch. Please note the OP is talking about a complete system crash and/or restart, not just chrome itself crashing. chrome itself can be built with any compiler, but if google-perftools is built with clang, crash! http://code.google.com/p/gperftools/issues/detail?id=394 There seem to be several problems with gperftools; compiled with gcc 4.2.1, there are at least 3 failures in its test suite (of 40 tests). Compiled with gcc 4.7 it doesn't even compile, since it erroneously tries to use backtrace_symbols(), which we don't provide. Compiled with clang 3.1, there are 12 failures. I assume this is because it is doing all kinds of tricky things with threads and re-implementing Yet Another Malloc, which seems to be very hard, as recent experience with head has shown. :) In any case, a good start would be to attempt to diagnose all the test failures that occur with clang only, to see if they indicate a problem in gperftools or clang itself. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
These kinds of hard locks often point at graphics driver problems, but normally Chrome relies on a driver whitelist that likely doesn't include any FreeBSD drivers. Did you perhaps set a flag somewhere to bypass a blacklist? You could try some command line flags like --blacklist-accelerated-compositing --blacklist-webgl to see if they help. (I found those on http://peter.sh/experiments/chromium-command-line-switches/ , not certain if they do what you need.) Another idea is to use strace/ktrace/truss into a log file to see what it was doing around the time of dying. On Wed, May 16, 2012 at 11:15 PM, Conrad J. Sabatier conr...@cox.net wrote: For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To make matters worse, no trace of what's happening is anywhere to be found. Nothing in any log files. The system doesn't drop into the kernel debugger, either. It's either a hard freeze or sudden reboot. I've tried rebuilding the chromium port, with both clang and gcc 4.6, to no avail. I've also updated the system sources several times this week and remade world/kernel. Nothing seems to help. I'm totally stumped as to how to determine what's going on here. Any suggestions as to how to obtain some useful info? Thanks! -- Conrad J. Sabatier conr...@cox.net ___ freebsd-chrom...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to freebsd-chromium-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On Thu, 17 May 2012 08:55:49 -0700 Evan Martin e...@chromium.org wrote: These kinds of hard locks often point at graphics driver problems, but normally Chrome relies on a driver whitelist that likely doesn't include any FreeBSD drivers. Did you perhaps set a flag somewhere to bypass a blacklist? You could try some command line flags like --blacklist-accelerated-compositing --blacklist-webgl to see if they help. (I found those on http://peter.sh/experiments/chromium-command-line-switches/ , not certain if they do what you need.) Another idea is to use strace/ktrace/truss into a log file to see what it was doing around the time of dying. Thanks. I tried those, and it still locked up. I finally just moved away ~/.config/chromium, and it started up OK. Luckily, I was able to restore pretty much everything from my synced data. Happy ending. :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On Thu, 17 May 2012 16:12:15 -0700 Evan Martin e...@chromium.org wrote: On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier conr...@cox.net wrote: Thanks. I tried those, and it still locked up. I finally just moved away ~/.config/chromium, and it started up OK. Luckily, I was able to restore pretty much everything from my synced data. It's a little surprising to me that a userspace app is able to nuke your system, but perhaps the bug is just something mundane like out of control memory allocations and it's just swapping. Yes, that *is* a little troubling. I'm always touting FreeBSD to people as being a rock-solid platform, so I was slightly embarrassed when this happened several times recently when I had a friend over. :-) I'm looking into some sysctl settings now that do seem to have the ability to trigger odd behavior with certain apps, e.g., kern.maxfiles, kern.maxfilesperproc, various shared mem settings, etc. Some apps will either mysteriously refuse to run, or crash just after startup, depending on the settings of these and similar. My chrome problem was no doubt related to my recently having tinkered with some chrome://flags settings. Conservatism and caution definitely seem to be called for with these! :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On Thu, 17 May 2012 07:20:51 -0500 Chuck Burns brea...@gmail.com wrote: On 5/17/2012 2:11 AM, John Hixson wrote: On Thu, May 17, 2012 at 01:15:54AM -0500, Conrad J. Sabatier wrote: For the last week or so, I've been unable to run chrome. Any attempt to start it up will cause the system either to freeze up or reboot. To add to this, I've had the same problem on 10-CURRENT for several months now. Are you guys building ports with clang? There's a known bug with google-perftools, when it's built with clang, chrome will crash upon launch. chrome itself can be built with any compiler, but if google-perftools is built with clang, crash! http://code.google.com/p/gperftools/issues/detail?id=394 Ah, yes, I remember you mentioning this a month or two ago (at least, I think it was you). Thanks for the reminder. I'm gonna make sure my /etc/make.conf specifies gcc for that port. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Chrome crashing system (amd64-10.0-CURRENT)
On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier conr...@cox.net wrote: Thanks. I tried those, and it still locked up. I finally just moved away ~/.config/chromium, and it started up OK. Luckily, I was able to restore pretty much everything from my synced data. It's a little surprising to me that a userspace app is able to nuke your system, but perhaps the bug is just something mundane like out of control memory allocations and it's just swapping. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
