[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #989: High CPU usage when calling signal handler
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #989: High CPU usage when calling signal handler multiple times |
Date: |
Sun, 03 Nov 2013 16:53:46 -0000 |
#989: High CPU usage when calling signal handler multiple times
-----------------------------+----------------------------------------------
Reporter: mario | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 4.9.0
Component: core libraries | Version: 4.8.x
Resolution: | Keywords: signal handling
-----------------------------+----------------------------------------------
Comment(by sjamaan):
I think #877 is due to the same underlying problem. There seems to be
something strange going on when handling interrupts. I think the reason
the bug goes away when messing with the continuation is because we're now
allowing interrupts to get handled via the "regular" way, through the GC
rather than explicitly by C_pending_interrupt.
I still not quite grok it, but this seems to be the case. A fix is by not
calling C_pending_interrupt, but this would kill the ability to save a
backlog of interrupts (effectively undoing
b7995839c0b481280bdeda117eb68bc0e78a40bf).
--
Ticket URL: <http://bugs.call-cc.org/ticket/989#comment:8>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
- Re: [Chicken-janitors] #989: High CPU usage when calling signal handler multiple times,
Chicken Trac <=