"Traced running time" is incorrect and meaningless on merged threads
See original GitHub issueProfile: https://share.firefox.dev/3ptwJzF
In this merged thread, for CFRunLoopRunSpecific
the sidebar shows “Traced running time: 138ms” and “Running samples: 2677”.
This does not make much sense.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
7. Helgrind: a thread error detector - Valgrind
Helgrind is a Valgrind tool for detecting synchronisation errors in C, C++ and Fortran programs that use the POSIX pthreads threading primitives.
Read more >ci/freedreno: add missing traces (!18616) · Merge requests · Mesa ...
game rendered with broken on-screen HUD; broken shadows; wrong colors. While fail would be: useless distorted image; missing important part of image (f.e....
Read more >Remove useless shortopt by WolfgangBai · Pull Request #7138 ...
I'm ok with this, but, kinda wish we'd fix the core instead to allow quoted @pparam's. All reactions. Sorry, something went wrong.
Read more >Initialization, Finalization, and Threads — Python 3.11.1 ...
Print a message each time a module is initialized, showing the place ... which will also affect non-Python uses of the console using...
Read more >[CLOSED] Password To Turned Off Or Reboot Phone
Pointless and redundant thread closed. @santhosh311983 said: yes ..there will be ample about of time to trace the phone before the phone does...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Well, somewhat - with a tid you could draw separate stack charts, maybe split the stack chart vertically into N horizontal bands, one band for each thread. The tid would also let us draw a more accurate CPU usage graph on a merged thread.
It might be worth to break out these
tid
ideas into separate issues, as they all seem pretty useful to me.