Can you identify the actual problem please?

The issue was caused by buffers not being released correctly when handling streamed responses.
The fix ensures that memory is freed promptly after each read operation, improving stability and preventing excessive RAM usage during large downloads.

That doesn't tell me what the problem is. Go has a garbage collector.

Once you've identified the actual problem can you send me a fix tojust fix that please? This patch rewrites the whole function changing everything for no good reason. It also has removed the pacer retries which are essential for reliability.

I don't mind looking at code that people have made with AI but I expect them to review it and tidy it first. Definitely remove the1)2)3) from the comments - they get out of date very quickly.

Maybe rewrite the whole function using the rest library which can do most of the work for you. Here is theOpen function from thebox backend which deals with range requests etc and should just work for you with minimal adaptation.

func (o*Object)Open(ctx context.Context,options...fs.OpenOption) (in io.ReadCloser,errerror) {ifo.id=="" {returnnil,errors.New("can't download - no id")}fs.FixRangeOption(options,o.size)varresp*http.Responseopts:= rest.Opts{Method:"GET",Path:"/files/"+o.id+"/content",Options:options,}err=o.fs.pacer.Call(func() (bool,error) {resp,err=o.fs.srv.Call(ctx,&opts)returnshouldRetry(ctx,resp,err)})iferr!=nil {returnnil,err}returnresp.Body,err}

Thank you