From owner-freebsd-bugs@freebsd.org Wed Jun 24 17:42:20 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2311915E3C for ; Wed, 24 Jun 2015 17:42:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 854861C3F for ; Wed, 24 Jun 2015 17:42:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5OHgKqp040575 for ; Wed, 24 Jun 2015 17:42:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 197842] kernel memory leak Date: Wed, 24 Jun 2015 17:42:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: netbsdrat@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2015 17:42:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197842 John Refling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netbsdrat@gmail.com --- Comment #1 from John Refling --- I have this problem NOW on 10.1-RELEASE. I am using memtest to test the RAM. It seems to me that I had this problem a long time ago, and there was bad RAM, and replacing that made the problem go away. That was a different machine from this one. I've made 2 passes of memtest without errors, however I'll let it run for a few more days to try to duplicate the temperature extremes. Anyhow, I have a program that I wrote that copies a lot of files to multiple disks, like 17,000 files. I ran it several days ago, and system crashes with the error in the original poster's post. I ran the program yesterday, and it ran to completion, no problem. Could be a temperature thing + RAM. I also put in some diagnostics on each loop of the program: char *delete = malloc(100); fprintf(stdout, "%p\n", delete); system("sysctl vm.kvm_free vm.kvm_size"); free(delete); The loop enters for each directory on the disk, not for each file, so there might be 900 loop entries. Now the vm.kvm_free and vm.kvm_size remain mostly constant. BUT the pointer to the delete is malloc()ed at 1000 (hex?) bytes greater each time the loop enters !!! I don't do any malloc()s after main(). This is probably not a reliable way to test things, but it looks suspicious. !!! Is there a better way to get the amount of free memory at any instant, probably another sysctl parameter. Anyhow this is just very frustrating and hard to track down. I had another issue that never got sorted out after years, on 9.1: http://lists.freebsd.org/pipermail/freebsd-questions/2013-November/254450.html Thanks, John Refling -- You are receiving this mail because: You are the assignee for the bug.