Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17698 - DrScheme built with --enable-noopt causes memory leak.
Attached to Project:
Arch Linux
Opened by David Brown (d3zd3z) - Sunday, 03 January 2010, 17:59 GMT
Last edited by Ionut Biru (wonder) - Sunday, 03 January 2010, 20:12 GMT
Opened by David Brown (d3zd3z) - Sunday, 03 January 2010, 17:59 GMT
Last edited by Ionut Biru (wonder) - Sunday, 03 January 2010, 20:12 GMT
|
DetailsDescription: DrScheme built with --enable-noopt, causes memory leak.
Additional info: drscheme - 4.2.3-1 Steps to reproduce: The attached program causes mzscheme to leak memory on x86_64. I rebuilt drscheme without the --enable-noopt config option, and that version does not leak memory. As far as I can tell, the --enable-noopt flag was in the debian package descriptor, but was removed many years ago, since nobody knew why it was there. It now appears to actually be causing a problem. The leak only appears on the x86_64 version, in the binary in the extra repository. Adding '-j' to disable JIT also prevents the leak, this seems to be some interaction between JIT, continuations and the lack of an optimizer. Upstream binary distributions are not built with --enable-noopt. The fix is easy, just remove '--enable-noopt' from the PKGBUILD file. |
This task depends upon
Comment by David Brown (d3zd3z) -
Sunday, 03 January 2010, 18:00 GMT
Not sure if this got attached.
leak.ss
(0.2 KiB)