[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU437-SMTP1619EF295C4A1463E8B5A1C0B20@phx.gbl>
Date: Sat, 20 Sep 2014 16:41:14 -1000
From: Scott Valentine <scottvalen@...mail.com>
To: lua-l@...ts.lua.org, musl@...ts.openwall.com
Subject: LUA + musl, garbage collection issue?
I have been testing OpenWRT builds using musl as the libc on arm and mips targets, and I have run into an issue which appears to be related to lua.
Essentially, when using the luci web interface to upload a file to the device, I am running into a memory exhaustion problem. A 6 MB upload results in nearly 70MB of memory allocation.
On smaller targets (i.e. 64MB RAM), it pretty much just locks up the system until the watchdog timer expires and reboots.
On bigger targets with enough RAM, the process completes and the memory is freed, but I think this is because the lua process exits.
On eglibc and uclibc builds I only see marginal memory increases during the upload, mostly do to the file getting written to tmpfs.
I'm having trouble tracking down where the issue is, but it looks like lua exclusively uses realloc for managing memory. Is this correct?
I noticed that in order to free memory, it basically calls realloc with 0 as the new size. Is this something musl doesn't handle well?
I'm trying a rebuild with a check for n == 0 in musl's realloc function to just free the pointer, and I'll report back.
What is "the right thing to do" to fix this? Should lua not be using realloc to free memory, or should musl handle the case better, if, in fact this is the problem?
Regards,
-Scott V.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
