Jorge Manrubia

Hey @ivoanjo, it totally looks like that. After setting `config.profiling.advanced.code_provenance_enabled = false` the memory leak problem seems solved. I'll leave this running for some time to be sure and get...

Confirmed it's that feature @ivoanjo: 

> Could I ask you to open a ticket with support via https://docs.datadoghq.com/help/ l @ivoanjo I just opened it (#821036)

I've been running some more tests and found some interesting things: - I confirm that the problem happens when profiling is enabled. - The problem happens when instrumenting `resque`. I...

Hey folks I'll get more info about it this week. It's on my radar, I just need to allocate time for it.

I patched this for `active_job` like this: ```ruby module DatadogSetErrorOnActiveJobPatch def set_common_tags(span, payload) super report_if_exception(span, payload) end end Datadog::Tracing::Contrib::ActiveJob::Event::ClassMethods.prepend DatadogSetErrorOnActiveJobPatch ``` Currently, `active_job` APM instrumentation relies on Rails instrumentation but...

Hey @cantino, I am about to take a flight. I'll look at this as soon as I can. In the next days I'll be a little bit disconnected though.

Also, it would be helpful if you can fork and push a failing spec

Thanks for reporting the problem. It seems there are some issues with Rails 4.1 due to AR changes. I haven't found time for looking into them yet. I will do...

Yes, we should fix this at the library: `local_time` should monitor mutations in the content so that it can reprocess the value when those happens. A workaround right now is...