-
### Description
When running unit tests we can see that the heap size increases with every spec file. There must be a memory leak somewhere. It might be related to the way unit tests are written bu…
-
**Describe the bug**
Using `weak` on a `Sendable` class leads to a bad diagnostic.
**Steps To Reproduce**
```swift
final class A: NSObject, Sendable {
lazy var a: String = "test"
}
```
…
-
**Describe the bug**
I found a memory leak in AnyAddress within the Kotlin package of Wallet Core.
```
dependencies {
implementation "com.trustwallet:wallet-core-kotlin-android:4.1.7"
}
```
…
10gic updated
5 hours ago
-
In this example, each time I press "Click", 50M of ram is allocated. It is never reclaimed, I can push 30 pages and take up 1.5gb, despite there only ever being 1 page on the nav stack. GC never kicks…
-
The following code:
``` haxe
class Main {
static function main() {
Test2.somethingElse(10);
}
}
class Test {
@:generic public static function something(t:T) {
return t;
}
}
@:forwar…
-
Surelog, at least when used as a library, has significant memory leaks.
First discovered in systemverilog-plugin, but later verified with basic Surelog examples (e.g. `hellouhdm`).
Brief look at log…
-
-
### Discord username (optional)
_No response_
### Describe the bug
On seemingly random occasions, when I open a new pane via Command+D, a massive .zsh script for the warp configuration is leaked in…
-
GC is designed around the invariant that there is a set of blocks from tail to head,
each block stores a set of changes, and storage supports adding to head and removing from tail.
To support this i…
-
Generated code does not actually call `free_mem`.
In the context of external functions, memory leaks are possible.