Thread overview | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
February 25, 2016 [Issue 15723] GC memory leakade depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 --- Comment #1 from Sobirari Muhomori <dfj1esp02@sneakemail.com> --- That's probably zlib's crc table: 2048 random pointers in bss. Does your application use zlib? -- |
February 25, 2016 [Issue 15723] GC memory leakade depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 --- Comment #2 from Denis Shelomovskij <verylonglogin.reg@gmail.com> --- (In reply to Sobirari Muhomori from comment #1) > That's probably zlib's crc table: 2048 random pointers in bss. So it looks like we actually can't use C libraries statically linked with D code as it will make GC almost useless. > Does your application use zlib? I have provided the whole test application in the description. As for my utility, yes it does use zlib. -- |
February 26, 2016 [Issue 15723] GC memory leakade depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 --- Comment #3 from Sobirari Muhomori <dfj1esp02@sneakemail.com> --- Yes, if C library has lots of random numbers in .data and .bss sections, that will be a problem. We can try to put crc table into .rdata section and exclude .rdata from GC roots (if not already). -- |
February 26, 2016 [Issue 15723] GC memory leakade depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 --- Comment #4 from Sobirari Muhomori <dfj1esp02@sneakemail.com> --- Though D can use this pattern too, so it's not only C library problem. -- |
February 26, 2016 [Issue 15723] GC memory leakage depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 Denis Shelomovskij <verylonglogin.reg@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|GC memory leakade depending |GC memory leakage depending |on source code size |on source code size -- |
May 05, 2017 [Issue 15723] GC memory leakage depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 calex <calex+bugzilla-mail@aristoweb.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |calex+bugzilla-mail@aristow | |eb.net -- |
June 07, 2019 [Issue 15723] GC memory leakage depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 anonymous4 <dfj1esp02@sneakemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=19947 -- |
June 07, 2019 [Issue 15723] GC memory leakage depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 Dennis <dkorpel@live.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkorpel@live.nl --- Comment #5 from Dennis <dkorpel@live.nl> --- *** Issue 18900 has been marked as a duplicate of this issue. *** -- |
June 12, 2019 [Issue 15723] GC memory leakage depending on source code size | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=15723 Rainer Schuetze <r.sagitario@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |r.sagitario@gmx.de Resolution|--- |FIXED --- Comment #6 from Rainer Schuetze <r.sagitario@gmx.de> --- Use command line option "--DRT-scanDataSeg=precise" or embed it into the binary with rt_options. -- |
Copyright © 1999-2021 by the D Language Foundation