You are not logged in.

#1 2011-08-05 23:11:00

WiLLiE
Member
From: Sweden
Registered: 2005-02-27
Posts: 133

[SOLVED] ./configure memoryleak

Hi all.

My system has been stable as a rock since I (re)installed it a few months ago. Until now that is.
Whenever I'm launching ./configure, the thread keeps spawning itself until my memory is full (3GB), and as a result everything is extremly sluggish. (i've tried this on multiple packages, both in AUR and from abs)
I have to run "killall configure" multiple times, to get my memory back (and CPU).

I don't know what could have caused this to happen, I havent installed a new kernel or anything like that.
The only new things I installed today where pekwm, lxde, xscreensaver (and a few others) and configured them.

A snipped from my errors.log:

Aug  6 00:41:16 localhost kernel: [ 1755.257845] Out of memory: Kill process 30022 (configure) score 2 or sacrifice child
Aug  6 00:41:16 localhost kernel: [ 1755.257850] Killed process 30032 (configure) total-vm:12284kB, anon-rss:6228kB, file-rss:0kB
Aug  6 00:41:45 localhost kernel: [ 1785.124984] Out of memory: Kill process 30210 (configure) score 2 or sacrifice child
Aug  6 00:41:45 localhost kernel: [ 1785.124988] Killed process 30215 (configure) total-vm:12252kB, anon-rss:6148kB, file-rss:0kB
Aug  6 00:44:23 localhost kernel: [ 1944.349554] Out of memory: Kill process 30453 (configure) score 2 or sacrifice child
Aug  6 00:44:23 localhost kernel: [ 1944.349558] Killed process 30453 (configure) total-vm:12428kB, anon-rss:6264kB, file-rss:0kB
Aug  6 00:44:23 localhost kernel: [ 1944.398311] Out of memory: Kill process 30459 (configure) score 2 or sacrifice child
Aug  6 00:44:23 localhost kernel: [ 1944.398316] Killed process 30476 (configure) total-vm:12284kB, anon-rss:6228kB, file-rss:0kB
Aug  6 00:44:23 localhost kernel: [ 1944.420913] Out of memory: Kill process 30459 (configure) score 2 or sacrifice child
Aug  6 00:44:23 localhost kernel: [ 1944.420917] Killed process 30459 (configure) total-vm:12284kB, anon-rss:6220kB, file-rss:0kB

Dmesg shows a massive list of:

[ 1944.420842] [30791]  1000 30791     3060     1529   0       0             0 configure
[ 1944.420846] [30792]  1000 30792     3591     2056   1       0             0 configure
[ 1944.420850] [30793]  1000 30793     3115     1586   1       0             0 configure
[ 1944.420855] [30794]  1000 30794     3064     1539   1       0             0 configure
[ 1944.420859] [30795]  1000 30795     3065     1542   1       0             0 configure
[ 1944.420863] [30796]  1000 30796     3108     1568   1       0             0 configure
[ 1944.420868] [30797]  1000 30797     3065     1542   1       0             0 configure
[ 1944.420876] [30799]  1000 30799     3065     1543   0       0             0 configure
[ 1944.420880] [30800]  1000 30800     3108     1569   0       0             0 configure
[ 1944.420884] [30801]  1000 30801     3591     2056   0       0             0 configure
[ 1944.420889] [30802]  1000 30802     3064     1540   0       0             0 configure
[ 1944.420893] [30803]  1000 30803     3065     1545   0       0             0 configure
[ 1944.420897] [30804]  1000 30804     3115     1588   0       0             0 configure

So, where to start, what to do?

Edit: The kernel is 2.6.39, on i686.

Edit2: And now I tried an autogen.sh script, same result except this time it was libtoolize that spawned forever.....

Last edited by WiLLiE (2011-08-07 10:57:05)

Offline

#2 2011-08-06 13:03:02

WiLLiE
Member
From: Sweden
Registered: 2005-02-27
Posts: 133

Re: [SOLVED] ./configure memoryleak

Noone? Perhaps i'm in the wrong section?

Offline

#3 2011-08-06 17:11:10

hauzer
Member
From: Belgrade, Serbia
Registered: 2010-11-17
Posts: 279
Website

Re: [SOLVED] ./configure memoryleak

No, most of the people just hit the "Topics: New" at the top right of the page. Being in a specific section doesn't contribute to the lack of responses. And I really have nothing to say on topic. tongue


Vanity of vanities, saith the Preacher, vanity of vanities; all is vanity.
What profit hath a man of all his labour which he taketh under the sun?
All the rivers run into the sea; yet the sea is not full; unto the place from whence the rivers come, thither they return again.
For in much wisdom is much grief: and he that increaseth knowledge increaseth sorrow.

Offline

#4 2011-08-07 10:55:44

WiLLiE
Member
From: Sweden
Registered: 2005-02-27
Posts: 133

Re: [SOLVED] ./configure memoryleak

Apparently it was kernel-related. I installed the 3.0 kernel and now i can compile again smile

Strange problem though, since I have not done anything kernel related for atleast 3 weeks.

Offline

#5 2011-08-07 11:40:23

ShionjiYuuko
Member
Registered: 2011-07-31
Posts: 64

Re: [SOLVED] ./configure memoryleak

I use kernel26 and ./configure never gives me a problem, maybe something wrong with bash?
need another case, this makes me curious... I'll wait for answer from Linux sages...


始まりの荒野を独り もう歩き出してるらしい、僕は灰になるまで僕で有り続けたい
http://about.me/nnhnkn | http://identi.ca/nnhzkn

Offline

#6 2011-09-08 18:56:04

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 779

Re: [SOLVED] ./configure memoryleak

I have the exact same problem on Kernel 3.1-rc5. I'll try reinstalling kernel 3.0. It's weird how this only happens to autotools scripts.


Current system: Lenovo W520
Unity-for-Arch repos' build statuses and old packages: https://jenkins.noobdev.io/

Offline

#7 2011-09-08 20:26:57

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: [SOLVED] ./configure memoryleak

Hmmm... I doubt the problem has anything to do with kernel. I had exactly the same issue today and after an hour or so I figured out the culprit was badly compiled dwm (after I had run make clean prior to make everything was OK again). The messages were *the same* as WiLLiE's, though. I realized that the problem lies somewhere else when I ran make in console instead of urxvt, where compilation went on smoothly. It never happened to me before. Odd.


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#8 2011-09-08 21:33:56

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 779

Re: [SOLVED] ./configure memoryleak

That's really weird. It happens to me with any configure or autotools script under any user. I have no idea what could have caused this.


Current system: Lenovo W520
Unity-for-Arch repos' build statuses and old packages: https://jenkins.noobdev.io/

Offline

#9 2011-09-09 14:35:34

jmartl109
Member
Registered: 2011-03-17
Posts: 24

Re: [SOLVED] ./configure memoryleak

I'm having this problem too. Unclear if it's kernel-related, as I'm running 3.0 (specifically, the latest 3.0.4-1) which seemed to solve it for others. For me the problem does not have anything to do with X (same crash when running ./configure in the console). I'm getting the same dmesg errors as the OP; here is more from /var/log/messages.log:

Sep  8 16:05:48 localhost kernel: [  137.720570] ACPI: EC: GPE storm detected, transactions will use polling mode
Sep  8 16:05:51 localhost kernel: [  141.084635] configure invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0, oom_score_adj=0
Sep  8 16:05:51 localhost kernel: [  141.084640] configure cpuset=/ mems_allowed=0
Sep  8 16:05:51 localhost kernel: [  141.084643] Pid: 3957, comm: configure Tainted: P        W   3.0-ARCH #1
Sep  8 16:05:51 localhost kernel: [  141.084645] Call Trace:
Sep  8 16:05:51 localhost kernel: [  141.084653]  [<c01d2e25>] dump_header.isra.6+0x85/0x1e0
Sep  8 16:05:51 localhost kernel: [  141.084657]  [<c01a52bc>] ? __delayacct_freepages_end+0x2c/0x40
Sep  8 16:05:51 localhost kernel: [  141.084660]  [<c028917f>] ? security_real_capable_noaudit+0x3f/0x70
Sep  8 16:05:51 localhost kernel: [  141.084663]  [<c01d316c>] oom_kill_process+0x5c/0x240
Sep  8 16:05:51 localhost kernel: [  141.084666]  [<c01d30be>] ? oom_badness+0xbe/0x110
Sep  8 16:05:51 localhost kernel: [  141.084668]  [<c01d341c>] ? select_bad_process.constprop.12+0xcc/0x100
Sep  8 16:05:51 localhost kernel: [  141.084671]  [<c01d371f>] out_of_memory+0xbf/0x1d0
Sep  8 16:05:51 localhost kernel: [  141.084674]  [<c01d6ff1>] __alloc_pages_nodemask+0x6f1/0x700
Sep  8 16:05:51 localhost kernel: [  141.084678]  [<c020919c>] new_slab+0x18c/0x1a0
Sep  8 16:05:51 localhost kernel: [  141.084681]  [<c044eb12>] __slab_alloc.isra.54.constprop.59+0x1a4/0x2e9
Sep  8 16:05:51 localhost kernel: [  141.084685]  [<c014443e>] ? dup_mm+0x1ce/0x5a0
Sep  8 16:05:51 localhost kernel: [  141.084687]  [<c0209673>] kmem_cache_alloc+0x133/0x140
Sep  8 16:05:51 localhost kernel: [  141.084690]  [<c02889ba>] ? cap_vm_enough_memory+0x4a/0x60
Sep  8 16:05:51 localhost kernel: [  141.084692]  [<c014443e>] ? dup_mm+0x1ce/0x5a0
Sep  8 16:05:51 localhost kernel: [  141.084694]  [<c014443e>] dup_mm+0x1ce/0x5a0
Sep  8 16:05:51 localhost kernel: [  141.084696]  [<c01453c8>] copy_process+0xb88/0x10e0
Sep  8 16:05:51 localhost kernel: [  141.084699]  [<c0289b74>] ? security_file_alloc+0x14/0x20
Sep  8 16:05:51 localhost kernel: [  141.084701]  [<c0145a12>] do_fork+0xb2/0x2f0
Sep  8 16:05:51 localhost kernel: [  141.084704]  [<c010ba14>] sys_clone+0x34/0x40
Sep  8 16:05:51 localhost kernel: [  141.084707]  [<c0454d19>] ptregs_clone+0x15/0x3c
Sep  8 16:05:51 localhost kernel: [  141.084709]  [<c0454bdf>] ? sysenter_do_call+0x12/0x28
Sep  8 16:05:51 localhost kernel: [  141.084711] Mem-Info:
Sep  8 16:05:51 localhost kernel: [  141.084713] DMA per-cpu:
Sep  8 16:05:51 localhost kernel: [  141.084715] CPU    0: hi:    0, btch:   1 usd:   0
Sep  8 16:05:51 localhost kernel: [  141.084716] CPU    1: hi:    0, btch:   1 usd:   0
Sep  8 16:05:51 localhost kernel: [  141.084718] Normal per-cpu:
Sep  8 16:05:51 localhost kernel: [  141.084719] CPU    0: hi:  186, btch:  31 usd:   0
Sep  8 16:05:51 localhost kernel: [  141.084721] CPU    1: hi:  186, btch:  31 usd:   0
Sep  8 16:05:51 localhost kernel: [  141.084722] HighMem per-cpu:
Sep  8 16:05:51 localhost kernel: [  141.084724] CPU    0: hi:  186, btch:  31 usd:   0
Sep  8 16:05:51 localhost kernel: [  141.084725] CPU    1: hi:  186, btch:  31 usd:   0
Sep  8 16:05:51 localhost kernel: [  141.084729] active_anon:388873 inactive_anon:8371 isolated_anon:0
Sep  8 16:05:51 localhost kernel: [  141.084730]  active_file:3696 inactive_file:25632 isolated_file:0
Sep  8 16:05:51 localhost kernel: [  141.084731]  unevictable:0 dirty:503 writeback:0 unstable:0
Sep  8 16:05:51 localhost kernel: [  141.084732]  free:73265 slab_reclaimable:1452 slab_unreclaimable:186476
Sep  8 16:05:51 localhost kernel: [  141.084733]  mapped:12098 shmem:249 pagetables:8302 bounce:0
Sep  8 16:05:51 localhost kernel: [  141.084737] DMA free:4244kB min:784kB low:980kB high:1176kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15804kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:5520kB kernel_stack:0kB pagetables:112kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Sep  8 16:05:51 localhost kernel: [  141.084741] lowmem_reserve[]: 0 865 2767 2767
Sep  8 16:05:51 localhost kernel: [  141.084748] Normal free:43832kB min:44012kB low:55012kB high:66016kB active_anon:0kB inactive_anon:0kB active_file:52kB inactive_file:144kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:885944kB mlocked:0kB dirty:0kB writeback:0kB mapped:332kB shmem:0kB slab_reclaimable:5808kB slab_unreclaimable:740384kB kernel_stack:13904kB pagetables:33096kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:62754 all_unreclaimable? yes
Sep  8 16:05:51 localhost kernel: [  141.084752] lowmem_reserve[]: 0 0 15216 15216
Sep  8 16:05:51 localhost kernel: [  141.084758] HighMem free:244984kB min:512kB low:24700kB high:48892kB active_anon:1555492kB inactive_anon:33484kB active_file:14732kB inactive_file:102384kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1947720kB mlocked:0kB dirty:2012kB writeback:0kB mapped:48060kB shmem:996kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:32 all_unreclaimable? no
Sep  8 16:05:51 localhost kernel: [  141.084762] lowmem_reserve[]: 0 0 0 0
Sep  8 16:05:51 localhost kernel: [  141.084764] DMA: 3*4kB 3*8kB 0*16kB 3*32kB 4*64kB 4*128kB 3*256kB 1*512kB 2*1024kB 0*2048kB 0*4096kB = 4228kB
Sep  8 16:05:51 localhost kernel: [  141.084772] Normal: 129*4kB 100*8kB 50*16kB 30*32kB 24*64kB 9*128kB 7*256kB 7*512kB 4*1024kB 2*2048kB 6*4096kB = 43908kB
Sep  8 16:05:51 localhost kernel: [  141.084778] HighMem: 6*4kB 9*8kB 4*16kB 3*32kB 4*64kB 3*128kB 6*256kB 8*512kB 5*1024kB 2*2048kB 56*4096kB = 245120kB
Sep  8 16:05:51 localhost kernel: [  141.084785] 29553 total pagecache pages
Sep  8 16:05:51 localhost kernel: [  141.084787] 0 pages in swap cache
Sep  8 16:05:51 localhost kernel: [  141.084788] Swap cache stats: add 0, delete 0, find 0/0
Sep  8 16:05:51 localhost kernel: [  141.084790] Free swap  = 2929660kB
Sep  8 16:05:51 localhost kernel: [  141.084791] Total swap = 2929660kB
Sep  8 16:05:51 localhost kernel: [  141.090884] 784127 pages RAM
Sep  8 16:05:51 localhost kernel: [  141.090887] 556817 pages HighMem
Sep  8 16:05:51 localhost kernel: [  141.090888] 76510 pages reserved
Sep  8 16:05:51 localhost kernel: [  141.090889] 1166487 pages shared

Offline

#10 2011-09-09 21:56:24

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 779

Re: [SOLVED] ./configure memoryleak

I just reinstalled my system and still have the same problem. It has to be something related to a recent update...

EDIT: Here's my pacman.log from a fresh install. Yaourt and package-query compiled fine, so something install after it must have screwed it up: http://pastie.org/private/4o4xg0ptpqzqsnyxbt65q

Last edited by chenxiaolong (2011-09-09 22:36:25)


Current system: Lenovo W520
Unity-for-Arch repos' build statuses and old packages: https://jenkins.noobdev.io/

Offline

#11 2011-09-09 23:40:59

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 779

Re: [SOLVED] ./configure memoryleak

I just ran an upgrade on another computer and now get this problem. So one of these packages shown in the log must have caused this problem: http://pastie.org/2511134


Current system: Lenovo W520
Unity-for-Arch repos' build statuses and old packages: https://jenkins.noobdev.io/

Offline

#12 2011-09-09 23:50:26

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: [SOLVED] ./configure memoryleak

Unfortunately, the problem persists for me as well, even in bare X with a single terminal instance. I have no clue how to track it down -- it's enough to run ./configure --help for my system to start choking and rapidly lose stability. My setup is pretty minimal based on the stock kernel 3.0.4 (i686) and with very few background processes running. Sniffing around the web I haven't found any similar case but one recorded ages ago on a Debian Sparc system. Any help will be highly appreciated then.


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#13 2011-09-09 23:54:01

karol
Archivist
Registered: 2009-05-06
Posts: 25,425

Re: [SOLVED] ./configure memoryleak

I suggest you guys start a new thread and maybe link to this one - it's solved for OP.

Offline

#14 2011-09-10 00:14:36

ploub
Member
Registered: 2007-05-16
Posts: 128

Re: [SOLVED] ./configure memoryleak

karol wrote:

I suggest you guys start a new thread and maybe link to this one - it's solved for OP.

I already did - it's here wink

Offline

#15 2011-09-10 00:15:49

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 779

Re: [SOLVED] ./configure memoryleak

I've found the source of the problem. The problematic package is pkgtools version 23-1. Hopefully this will help others that also have this problem. I have already reported the bug to the developer.

Note: after removing the package, a reboot is required.


Current system: Lenovo W520
Unity-for-Arch repos' build statuses and old packages: https://jenkins.noobdev.io/

Offline

#16 2011-09-10 00:49:27

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: [SOLVED] ./configure memoryleak

A reboot is not required. It's sufficient to logout, or even just run 'unset command_not_found_handle'. I've pushed pkgtools 23-2 to [community] to stop the bleeding.

Offline

#17 2011-09-10 01:30:33

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: [SOLVED] ./configure memoryleak

Thank you!


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#18 2011-09-10 01:40:14

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 779

Re: [SOLVED] ./configure memoryleak

Thanks!!


Current system: Lenovo W520
Unity-for-Arch repos' build statuses and old packages: https://jenkins.noobdev.io/

Offline

Board footer

Powered by FluxBB