GNU bug report logs - #31110
27.0.50; profiler-reset errors if you have not cpu profiled

Previous Next

Package: emacs;

Reported by: Aaron Jensen <aaronjensen <at> gmail.com>

Date: Mon, 9 Apr 2018 11:35:02 UTC

Severity: minor

Tags: fixed, moreinfo, unreproducible

Found in version 27.0.50

Fixed in version 27.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 31110 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Aaron Jensen <aaronjensen <at> gmail.com>
Cc: 31110 <at> debbugs.gnu.org
Subject: Re: bug#31110: 27.0.50; profiler-reset errors if you have not cpu
 profiled
Date: Sat, 13 Jul 2019 17:33:17 +0200
Aaron Jensen <aaronjensen <at> gmail.com> writes:

>>From emacs -Q
> M-x profiler-start mem
> M-x profiler-stop
> M-x profiler-reset
>
> Expected:
>
> No error, mem profile would be reset.
>
> Actual:
>
> Error, mem profile is not reset.
>
> Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
>   profiler-cpu-log()
>   profiler-reset()

I'm unable to reproduce this bug on the Emacs trunk currently.  I seem
to remember some work being done in the profiler data storage area some
months back, so perhaps that fixed it?

Could you update and check whether this still fails for you?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 5 years and 318 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.