Yes. Thanks for your help. I've been reflecting on this and I have a couple
of observations:
1) In some ways, the suddenly bloated executable is useful because, as in
this case, it points to a design flaw in the program.
2) However, it was some weeks before I noticed that a problem had arisen
This was traced down to passing very large (multi-MB) types by value.
TL;DR, don't do that. See the issue for more details.
On Thursday, November 19, 2020 at 12:59:32 PM UTC-8 ren...@ix.netcom.com
wrote:
> Based on the OP it is occurring with 1.13,14,15
>
> > On Nov 19, 2020, at 2:19 PM, Ian L
Based on the OP it is occurring with 1.13,14,15
> On Nov 19, 2020, at 2:19 PM, Ian Lance Taylor wrote:
>
> On Thu, Nov 19, 2020 at 11:34 AM stephen.t@gmail.com
> wrote:
>>
>> I have a reasonably sized project that produces executables that have
>> ballooned in size between two relatively
On Thu, Nov 19, 2020 at 11:34 AM stephen.t@gmail.com
wrote:
>
> I have a reasonably sized project that produces executables that have
> ballooned in size between two relatively simple commits.
>
> I've tested with three compiler versions and in each case the executable size
> is significantl
Filed https://github.com/golang/go/issues/42729
On Fri, Nov 20, 2020 at 6:34 AM stephen.t@gmail.com <
stephen.t.illingwo...@gmail.com> wrote:
> Hello,
>
> I have a reasonably sized project that produces executables that have
> ballooned in size between two relatively simple commits.
>
> I've
