Right now, with the patches applied on 3.5.0, Chrome didn't freeze under out of memory conditions (2 OOM killer invocation). On Fri, Oct 5, 2012 at 4:44 PM, Josef Bacik <jbacik@xxxxxxxxxxxx> wrote: > On Fri, Oct 05, 2012 at 02:23:25PM -0600, Jérôme Poulin wrote: >> I guess I'll be the guy who will test out of memory conditions! Here's >> another stack further down the code. >> > > Ok that was just a warning, did the box keep going after that? I've fixed it up > and sent a patch, unapply all the patches I've given you and apply the new ones > I've just sent (there are 3) and see how that works for you. If you don't get > any BUG()'s but it's still hung then I'll need sysrq+w to see where you are > hung, we probably screw up unlocking in these codepaths somewhere. Thanks, > > Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
