Bug 1543447 Comment 20 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Stephen A Pohl [:spohl] from comment #19)
> (In reply to Eric Rahm [:erahm] from comment #18)
> > (In reply to Stephen A Pohl [:spohl] from comment #17)
> > > We have contacts, but we would need to have this type of problem analyzed and distilled in great detail before it would make sense to reach out to them, including easy steps to reproduce or some type of sample application that would trigger this behavior.
> > 
> > It's pretty basic, just run `atos` on `libxul`.
> 
> I meant: Is running this on 10.15 sufficient to reproduce the issue? Does it only occur after an update to Catalina (comment 13)? Does it happen on all systems that have been updated, or are there any other factors that need to be in place before this reproduces? Basically, once we have someone at Apple look into this we want to be sure that they can reproduce the issue.

It's been bad for a long time (this was file 8 months ago, a related bug 10 months ago, I look at perf a few years ago as well), I don't think upgrading to 10.15 is required. It just might be that the tools are worse now.
(In reply to Stephen A Pohl [:spohl] from comment #19)
> (In reply to Eric Rahm [:erahm] from comment #18)
> > (In reply to Stephen A Pohl [:spohl] from comment #17)
> > > We have contacts, but we would need to have this type of problem analyzed and distilled in great detail before it would make sense to reach out to them, including easy steps to reproduce or some type of sample application that would trigger this behavior.
> > 
> > It's pretty basic, just run `atos` on `libxul`.
> 
> I meant: Is running this on 10.15 sufficient to reproduce the issue? Does it only occur after an update to Catalina (comment 13)? Does it happen on all systems that have been updated, or are there any other factors that need to be in place before this reproduces? Basically, once we have someone at Apple look into this we want to be sure that they can reproduce the issue.

It's been bad for a long time (this was filed 8 months ago, a related bug 10 months ago, I look at perf a few years ago as well), I don't think upgrading to 10.15 is required. It just might be that the tools are worse now.
(In reply to Stephen A Pohl [:spohl] from comment #19)
> (In reply to Eric Rahm [:erahm] from comment #18)
> > (In reply to Stephen A Pohl [:spohl] from comment #17)
> > > We have contacts, but we would need to have this type of problem analyzed and distilled in great detail before it would make sense to reach out to them, including easy steps to reproduce or some type of sample application that would trigger this behavior.
> > 
> > It's pretty basic, just run `atos` on `libxul`.
> 
> I meant: Is running this on 10.15 sufficient to reproduce the issue? Does it only occur after an update to Catalina (comment 13)? Does it happen on all systems that have been updated, or are there any other factors that need to be in place before this reproduces? Basically, once we have someone at Apple look into this we want to be sure that they can reproduce the issue.

It's been bad for a long time (this was filed 8 months ago, a related bug 10 months ago, I looked at perf a few years ago as well), I don't think upgrading to 10.15 is required. It just might be that the tools are worse now.

Back to Bug 1543447 Comment 20