UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36

Steps to reproduce the problem:
1. Start a profile recording in Developer Tools > Profile
2. Execute a function that contains code which prevents v8 from optimizing function (such as a for of loop). My function(s) execute in the context of my extension in a content script.
3. Stop profile recording and review results
4. The non-optimized function will have a yellow warning triangle next to it in function list. Mousing over the triangle displays the message - Not Optimized: TryCatchStatement, regardless of the actual cause of the v8 bailout.

What is the expected behavior?
The actual reason for not optimizing the function should be displayed.

What went wrong?
I've tested this with the following v8 bailout reasons (none of the tested functions contained a try catch block): 1) For of loop, 2) assignment deconstruction, eg [a,b] = [1,2].
I tested by profiling functions with these statements and then replaced the statements with equivalents that don't cause a bailout (such as using forEach instead of for of). After replacing these statements, and running a new profile, the functions were optimized.

Did this work before? N/A 

Chrome version: 52.0.2743.82  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 22.0 r0