Skip to content

Commit

Permalink
opkg memory problem?
Browse files Browse the repository at this point in the history
01234567890123456789012345678901234567890123456789012345678901234567890123456789
When OE does 'opkg-cl install $EVERYTHING', all the memory leaks in opkg
start to accumulate. My guess is that somewhere a memory allocation failed
but was not checked for failure, then everything started to blow up.

Obviously, the memory leaks should be plugged (working on it...) and memory
allocations checked for failure (hopefully all sorted in opkg svn now). But
there's still a danger that large images will exhaust the supply of memory,
causing massive thrashing if nothing else.

The following is untested and only reduces that chances of this occuring,
but perhaps it makes sense to do something like this?
  • Loading branch information
grahamgower authored and zecke committed Jan 28, 2010
1 parent 4a6efa5 commit 945878c
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions classes/rootfs_ipk.bbclass
Expand Up @@ -53,9 +53,9 @@ fakeroot rootfs_ipk_do_rootfs () {
done
fi
fi
if [ ! -z "${PACKAGE_INSTALL}" ]; then
opkg-cl ${IPKG_ARGS} install ${PACKAGE_INSTALL}
fi
for i in ${PACKAGE_INSTALL}; do
opkg-cl ${IPKG_ARGS} install $i
done

export D=${IMAGE_ROOTFS}
export OFFLINE_ROOT=${IMAGE_ROOTFS}
Expand Down

0 comments on commit 945878c

Please sign in to comment.