
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Is there an existing issue for this?
Describe the bug
Using .NET 6 with
JSInterop.InvokeVoidAsync
, may cause memory leak, since the cacheFunction maps (on JS-side of JSInterop) isn't covered by garbage-collector.I don't use C# nor .NET 6. I'm just exploring how C# runtime calls JS functions.
The function documentation describes:
aspnetcore/src/JSInterop/Microsoft.JSInterop/src/JSRuntimeExtensions.cs
Lines 15 to 21 in c85baf8
Given that
"someScope.someFunction"
is a valid function. We can also consider thatsomeScope
could be one map (such asnew Map()
), in that case each index the internalcacheFunction
will also cached:aspnetcore/src/JSInterop/Microsoft.JSInterop.JS/src/src/Microsoft.JSInterop.ts
Lines 21 to 34 in 6969db9
Expected Behavior
It should not cause memory leak, and not implicit cache, or must be covered by GC somehow.
Or, otherwise, that behavior must be documented. It must inform that
JsRuntime.InvokeVoidAsync
caches the argument values, and that isn't suppose to be used for accessing mutable methods and maps (or anything that implementsget
directly). _Consider the code below as example, since it acts like a "function-table" that always return a valid value. That code is valid and a valid JS, and works. It also works currently, but causes memory leaks due to .NET 6 implementation.Steps To Reproduce
If we consider such function in Javascript:
If we call it using the following C# code:
It would cause a huge memory leak on JS-side of JSInterop. Since it would cache each
Convert.ToBase64String(b)
value into the_cachedFunctions
. The values from_cachedFunctions
is never cleared by .NET/C#.Exceptions (if any)
No response
.NET Version
6.0.101
Anything else?
dotnet --info
The text was updated successfully, but these errors were encountered: