Measure the elapsed time of ShellExecuteByExplorer
Categories
(Core :: Widget: Win32, enhancement, P3)
Tracking
()
People
(Reporter: toshi, Assigned: toshi)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
Bug 1646986 told us ShellExecuteByExplorer
could block the thread under some unknown circumstances. It would be good to collect data of the elapsed time of that API to see how common such a situation is.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
This patch adds a new measurement to the histogram about the elapsed time
of ShellExecuteByExplorer
. If ShellExecuteByExplorer takes long in
a considerable number of instances, we need to consider fixing bug 1646986.
Comment 3•5 years ago
|
||
Comment 5•5 years ago
|
||
bugherder |
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
Attaching the screenshot of the histogram. The duration is distributed without any unexpected peaks. There are instances where the API takes a long time, but the volume is not so high. No immediate action is needed.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 8•5 years ago
|
||
Now that we've concluded no immediate action is needed for slow
ShellExecuteByExplorer, SHELLEXECUTEBYEXPLORER_DURATION_MS
is
no longer needed.
Assignee | ||
Comment 9•5 years ago
|
||
Getting data from Beta 80. The trend is the same as Nightly. There is just one peak, without having an additional peak that would be caused by a common factor.
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
bugherder |
Comment 12•5 years ago
|
||
Change the status for beta to have the same as nightly and release.
For more information, please visit auto_nag documentation.
Description
•