|
Hannes Payer
@
PayerHannes
Munich, Bavaria
|
|
Google|Chrome|V8• Tech Lead and Manager of @v8js • Researcher • Skier|Surfer|Climber|Mountaineer • 💚Outdoors • Austrian • opinions are my own
|
|
|
25
Tweetovi
|
83
Pratim
|
376
Osobe koje vas prate
|
| Tweetovi |
|
Hannes Payer
@PayerHannes
|
26. srp |
|
I don’t think they are ugly from an implementation perspective. They unfortunately do have an inherent pause time problem.
The main problem I see is that they make GC observable which creates a new class of bugs complaining that GC is not happening. Won’t fix!
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
29. svi |
|
JavaScript memory can be displayed using the heap snapshotting mechanism in Chrome Dev Tools.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
29. svi |
|
The JavaScript heap is currently limited to 2G of memory.
The task manager has a couple of categories which can show you where memory is going (right click on the title bar to enable them).
Or take a performance trace using chrome://tracing (with memory-infra category enabled)
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
29. svi |
|
Got it. I am afraid that we do not have a general mechanism to flush out leaks. Often a leak can be triggered by performing repetitive actions on webpages with a high frequency.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
29. svi |
|
Can you repro? If yes, please file a crbug.com.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
1. ožu |
|
Yes it would. The principal algorithm is independent of the host language.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
5. pro 2018. |
|
I am wondering whether it measures the accumulative GC time on the main thread per full GC cycle or the main pause of a full GC. A main pause of 100+ms would still be not great. I would love to see a performance trace if this is the case.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
5. pro 2018. |
|
Nice! What does GC Pause Time measure?
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
24. lis 2018. |
|
Next time it will be in Athens \o/
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
27. lip 2018. |
|
he is compiling v8 again \o/
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
19. tra 2018. |
|
Brace yourself, concurrently marking the C++ heap of Blink is going to happen @mlippautz pic.twitter.com/ZPTJMEqcJW
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
19. tra 2018. |
|
Take a deep breath, the web is big @mlippautz pic.twitter.com/FeAZS5FeIh
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
18. tra 2018. |
|
Makes sense. We should figure out how to do even more detailed attribution. Showing e.g. the CSS would definitely be useful.
|
||
|
|
||
| Hannes Payer proslijedio/la je tweet | ||
|
PLDI
@PLDI
|
11. sij 2018. |
|
The International Symposium on Memory Management (ISMM) is co-located with PLDI. Submit by February 15. conf.researchr.org/home/ismm-2018
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
20. ožu 2017. |
|
that may be tricky due to some constraints on the size field. we will have a look.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
3. ožu 2017. |
|
they will be sad when the finalizers are never called
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
3. ožu 2017. |
|
finalizers come with a performance penalty. A fast GC does not know about dead objects.
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
3. ožu 2017. |
|
GC could trace both JS and wasm \o/
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
24. velj 2017. |
|
Happy to see our memory reduction effort paying off in the real-world blog.wikimedia.org/2017/02/17/nod…
|
||
|
|
||
|
Hannes Payer
@PayerHannes
|
9. velj 2017. |
|
Big JS heaps and nice debugging story for memory leaking web apps v8project.blogspot.de/2017/02/one-sm…
|
||
|
|
||