Re: MPS: profiler

[Ihor Radchenko]

Eli Zaretskii <eliz@gnu.org> writes:

>> I'm still not sure. What I'm trying to say is that we need to be sure
>> that there are no windows left in which things can change. I'd be most
>> comfortable ATM if the first thing the SIGPROF handler does is check
>> is_busy and immediately returns, doing nothing.
>
> Does that solve the crashes reported here?

I can no longer reproduce on my side, after pulling the latest commit in
the branch - profiler does not lead to crashes in the reproducer I
provided and also using my main config.

Although, what is curious, I am now getting a sizable contribution of the
GC reported by the profiler:

       19193  93% + command-execute
        1131   5%   Automatic GC

If necessary, I can compare the above result with what happens on master.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>