From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter =?UTF-8?Q?M=C3=BCnster?= Newsgroups: gmane.emacs.bugs Subject: bug#15561: periodic timer stops running Date: Tue, 04 Mar 2014 10:11:16 +0100 Message-ID: <87siqyqqff.fsf@micropit.couberia.selfip.net> References: <87zjl8y4lx.fsf@micropit.couberia.selfip.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1393923737 15262 80.91.229.3 (4 Mar 2014 09:02:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Mar 2014 09:02:17 +0000 (UTC) Cc: Paul Eggert , 15561@debbugs.gnu.org To: Barry OReilly Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 04 10:02:25 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WKlEy-0002hl-W9 for geb-bug-gnu-emacs@m.gmane.org; Tue, 04 Mar 2014 10:02:21 +0100 Original-Received: from localhost ([::1]:43771 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKlEy-0004jM-LB for geb-bug-gnu-emacs@m.gmane.org; Tue, 04 Mar 2014 04:02:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39477) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKlEn-0004c3-Im for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2014 04:02:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKlEg-0006m2-9f for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2014 04:02:09 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:48607) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKlEg-0006ly-7O for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2014 04:02:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WKlEf-0008VP-Nh for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2014 04:02:01 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: Resent-From: Peter =?UTF-8?Q?M=C3=BCnster?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 04 Mar 2014 09:02:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15561 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15561-submit@debbugs.gnu.org id=B15561.139392369932660 (code B ref 15561); Tue, 04 Mar 2014 09:02:01 +0000 Original-Received: (at 15561) by debbugs.gnu.org; 4 Mar 2014 09:01:39 +0000 Original-Received: from localhost ([127.0.0.1]:49789 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WKlEI-0008Ui-Oh for submit@debbugs.gnu.org; Tue, 04 Mar 2014 04:01:39 -0500 Original-Received: from smtp01.smtpout.orange.fr ([80.12.242.123]:41710 helo=smtp.smtpout.orange.fr) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WKlEG-0008UZ-9N for 15561@debbugs.gnu.org; Tue, 04 Mar 2014 04:01:37 -0500 Original-Received: from micropit.couberia.selfip.net ([86.214.40.140]) by mwinf5d48 with ME id ZM1Z1n00H31SWiW03M1ZDX; Tue, 04 Mar 2014 10:01:34 +0100 Original-Received: by micropit.couberia.selfip.net (Postfix, from userid 1000) id 26624A60CF1; Tue, 4 Mar 2014 10:11:16 +0100 (CET) User-Agent: Gnus/5.13001 (=?UTF-8?Q?=E7=9C=9F?= Gnus v0.10) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:86520 Archived-At: On Tue, Mar 04 2014, Barry OReilly wrote: > Is it always the same timer that stops running, or have you seen > different timers in Emacs stop? Hi Barry, Different timers. > Could you come up with a recipe that allows us to reproduce the bug? I don't know. It would be difficult: - in happens only once or twice per day - the timers depend on my personal environment: checking email, news, Bitcoin value, the todo-list of my org-file and so on - some timers depend on idle-time Would it help, if I a add some code to the start and to the end of each timer function, that prints interesting information to the *Messages* buffer? And when it happens again, we would get some trace? -- Peter