# Profiling crashing or perhaps non-responsive - where to report?

**URL:** <https://discourse.julialang.org/t/profiling-crashing-or-perhaps-non-responsive-where-to-report/104879>\
**Category:** New to Julia\
**Created:** [October 11, 2023, 11:44pm UTC](https://discourse.julialang.org/t/profiling-crashing-or-perhaps-non-responsive-where-to-report/104879 "2023-10-11T23:44:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![orebas](https://avatars.discourse-cdn.com/v4/letter/o/bbe5ce/32.png) [@orebas](https://discourse.julialang.org/u/orebas)\
**Post date:** [October 20, 2023, 5:19pm UTC](https://discourse.julialang.org/t/profiling-crashing-or-perhaps-non-responsive-where-to-report/104879/3 "2023-10-20T17:19:24Z")

</div>

Hi, just to follow up on this. I believe there are a couple of separate things going on.

1. @profile does cause some “performance degradation”, which is known and to be expected. And perhaps it is reasonable for it to be 10x or 20x? I am not sure about that. So slow commands can be very very slow when I try to profile them.

As an example, the following is taking many minutes on my machine (perhaps it has crashed, I am not sure):

```julia
julia> using Profile
julia> @profile using ParameterEstimation

```

2)the terminal is not responding to ctrl-c. I have seen some other discussion of this (example: [cannot-catch-ctrl-c-gracefully](https://discourse.julialang.org/t/cannot-catch-ctrl-c-gracefully-in-this-script/79757/4)) Honestly this is not a big deal for me, the profiling problems are more concerning.

---

_[View the full topic](https://discourse.julialang.org/t/profiling-crashing-or-perhaps-non-responsive-where-to-report/104879)._