P-Y on Nostr: It's worth noting that usually LeakCanary runs on Android heap dumps. This is a JVM ...
It's worth noting that usually LeakCanary runs on Android heap dumps. This is a JVM unit test, so it's a JVM heap dump, and these can be funky.
The first step to investigating is always reproducing. It doesn't repro locally, only in CI... and rarely. So I need that heap dump file that was created in CI.
Published at
2024-05-30 15:57:58Event JSON
{
"id": "a020e7a049b9d9b91b9a95c690906ac795b1649a8a85d5b0443c997e4bdbcaeb",
"pubkey": "2b9c6c28bce249a1ef28497a2ec6f6c01bc7be0721124b8ce7da3e1592080c57",
"created_at": 1717084678,
"kind": 1,
"tags": [
[
"e",
"5f2620b961f64cd4ef25693b89a495153b519a3a9ec0ad486f420e9230d2c871",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://androiddev.social/users/py/statuses/112530861506979670",
"activitypub"
]
],
"content": "It's worth noting that usually LeakCanary runs on Android heap dumps. This is a JVM unit test, so it's a JVM heap dump, and these can be funky.\n\nThe first step to investigating is always reproducing. It doesn't repro locally, only in CI... and rarely. So I need that heap dump file that was created in CI.",
"sig": "63a91f75d6f389fbcfe6c79d42553d10de84a0a261d9152a524420c0c39708f2ddf8d647a40bf8a6bc695f0a565d9ee2a657d92cb740e472197dd3281bfbb471"
}
