yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #73351
[Bug 1777486] [NEW] Multiple profiler traces get same base_id
Public bug reported:
OpenStack Queens release.
With developer panel and profiler enabled, you can select "Profile
Current Page" to create a new profiler trace. That initializes a
profiler instance here:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/contrib/developer/profiler/middleware.py#L64
That instance is never deleted. The next time you select "Profile
Current Page", the test here finds the previous instance and returns it,
instead of creating a new instance:
https://github.com/openstack/osprofiler/blob/master/osprofiler/profiler.py#L59
So the previous base_id is reused for the new trace. When the trace
details are retrieved from the profiler database by searching for the
base_id, events from both first and second traces are returned.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1777486
Title:
Multiple profiler traces get same base_id
Status in OpenStack Dashboard (Horizon):
New
Bug description:
OpenStack Queens release.
With developer panel and profiler enabled, you can select "Profile
Current Page" to create a new profiler trace. That initializes a
profiler instance here:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/contrib/developer/profiler/middleware.py#L64
That instance is never deleted. The next time you select "Profile
Current Page", the test here finds the previous instance and returns
it, instead of creating a new instance:
https://github.com/openstack/osprofiler/blob/master/osprofiler/profiler.py#L59
So the previous base_id is reused for the new trace. When the trace
details are retrieved from the profiler database by searching for the
base_id, events from both first and second traces are returned.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1777486/+subscriptions
Follow ups