mirror of
https://github.com/golang/go
synced 2024-09-30 16:18:35 -06:00
e3f0bd94ad
Consider a pathological file that contains a single string that is 1GiB large. The current heuristic for allocating the events would create a slice that is 330M elements large, when only a small number of events would ever be needed. This may easily cause the analysis to OOM on the pathological file. Alleviate the consequences of a pathological file by imposing a maximum number of events. Change-Id: I937bb8a3f479866631c4895ac1e729458f6e5e34 Reviewed-on: https://go-review.googlesource.com/c/tools/+/227861 Run-TryBot: Joe Tsai <thebrokentoaster@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alan Donovan <adonovan@google.com> |
||
---|---|---|
.. | ||
analysis | ||
ast | ||
buildutil | ||
callgraph | ||
cfg | ||
expect | ||
gccgoexportdata | ||
gcexportdata | ||
internal | ||
loader | ||
packages | ||
pointer | ||
ssa | ||
types | ||
vcs |