November 03, 2016
https://issues.dlang.org/show_bug.cgi?id=9094

Jesse Phillips <Jesse.K.Phillips+D@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |Jesse.K.Phillips+D@gmail.co
                   |                            |m
         Resolution|WONTFIX                     |---

--- Comment #4 from Jesse Phillips <Jesse.K.Phillips+D@gmail.com> ---
I'm having this issue with Windows 64bit on 30MB files, and it appears is also affecting zip extraction of similar size. I'm reopening so the issue can be re-evaluated considering this isn't just a 32bit + gigabyte file issue.

Does anyone have a suggestion for manually releasing the expanded data when using std.zip.ZipArchive.expand() on a ArchiveMember?

--
April 21, 2019
https://issues.dlang.org/show_bug.cgi?id=9094

Rainer Schuetze <r.sagitario@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.sagitario@gmx.de

--- Comment #5 from Rainer Schuetze <r.sagitario@gmx.de> ---
With the precise GC enabled via "--DRT-gcopt=gc:precise
--DRT-scanDataSeg=precise"
the program no longer runs out of memory, but needs up to 500MB of memory (the
64-bit version runs with less than 200MB). Probably still some false pointers
on the stack.

--