UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Start the JavaScript profiler
2. Do something that will trigger some code
3. Stop the profiler
4. Look at the output stack trace

What is the expected behavior?
In this example I expect a single call to a particular function. I have proved that this is happening with by using break points and console.logs.

What went wrong?
The call stack looks split up into multiple calls, making it much more difficult to understand.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: n/a
OS Version: 10.0
Flash Version: 

Here's a formatted description explaining what's going on: https://stackoverflow.com/questions/48423996/understanding-the-chrome-performance-profile
 

Deleted: Profile.gif 213 KB

	Profile.gif 213 KB View Download