You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you look at a 1000 genome vcf and continuously side scroll, the amount of memory consumed can go up to high levels on the main thread (not web worker). The 1000 genomes vcf's already allocate a lot of memory due to serialization of the genotypes field, but the continuing increase in memory consumption seems odd. It can eventually go down, but the memory remains high and seems like it could be a bug somehow?
It's possible this is not a true memory leak, but i suppose even if not, the amount of memory used for browsing 1000 genomes type data should be brought under control e.g. by avoiding serialization of the genotype field
Example
Memory panel of devtools, showing >2gb consumption, tested in v1.3.0 just for checking if it affects older and newer versions
Allocation sampling panel, showing a large amount of memory dominated by one long shallow rectangle
The code that it points to for that rectangle
I was not sure why that particular bit of code would be "holding" the memory but i'm also not too familiar with memory profiling
The text was updated successfully, but these errors were encountered:
If you look at a 1000 genome vcf and continuously side scroll, the amount of memory consumed can go up to high levels on the main thread (not web worker). The 1000 genomes vcf's already allocate a lot of memory due to serialization of the genotypes field, but the continuing increase in memory consumption seems odd. It can eventually go down, but the memory remains high and seems like it could be a bug somehow?
It's possible this is not a true memory leak, but i suppose even if not, the amount of memory used for browsing 1000 genomes type data should be brought under control e.g. by avoiding serialization of the genotype field
Example
Memory panel of devtools, showing >2gb consumption, tested in v1.3.0 just for checking if it affects older and newer versions
Allocation sampling panel, showing a large amount of memory dominated by one long shallow rectangle
The code that it points to for that rectangle
I was not sure why that particular bit of code would be "holding" the memory but i'm also not too familiar with memory profiling
The text was updated successfully, but these errors were encountered: