UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. Use a wrapped console log function (in my case, logdown.js) for logging in your application
2. Blackbox the log wrapper via a regex in Devtool Settings>Blackboxing (in my case, '/logdown\.js$')
3. Reload the page with logging
4. Notice that although the logging wrapper file has a 'this script is blackboxed' header in the source inspector, logging is not resolving the non-framework location/line number as described here: https://gist.github.com/paulirish/c307a5a585ddbcc17242
5. Deleting and re-adding the blackboxing regex in Devtools settings will temporarily restore appropriate line numbers, but they will revert to the wrapped logger on page reload.

What is the expected behavior?
https://gist.github.com/paulirish/c307a5a585ddbcc17242

What went wrong?
Sometime between last week and this week, a Chrome update caused this regression

Did this work before? Yes Not sure, but I believe it was working last week

Chrome version: 60.0.3112.113  Channel: n/a
OS Version: OS X 10.12.6
Flash Version: 

For now, deleting and re-adding the blackboxing regex is a viable workaround. If this gets too annoying I'll figure out what version of Chrome broke this feature and update the ticket.