Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
While working on BaselineProfileRule, I noticed that all of the launches in simple tests are warm, since we don't kill the process.
This means we're only ever hitting actual process startup code once, even if we loop many times.
We should consider making it easier to define a StartupMode.COLD startup, but if so, also make sure to correctly handle broadcasting the SIGUSR1 when the app is killed.
If platform is extremely aggressive about including cold startup in the profile, this may not be necessary, but we should check if we miss anything if the dev calls killProcess explicitly since we're not sending the SIGUSR1.