From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-user@gnu.org
Subject: Re: Potluck - thread safe event loop with await semantics
Date: Tue, 23 Feb 2016 16:49:10 +0000 [thread overview]
Message-ID: <20160223164910.6a40c66c@dell.homenet> (raw)
In-Reply-To: <20160223120916.2ea94c7e@dell.homenet>
On Tue, 23 Feb 2016 12:09:16 +0000
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
[snip]
> As regards guile-gnome, I guess the problem may well be to do with the
> operation of the garbage collector. However I suspect it is caused by
> too eager collection rather than too conservative collection - there
> is no obvious sign of excess memory usage. Probably the collector
> sometimes frees memory still in use by the wrapper when the wrapper is
> invoked in a multi-threaded context.
And also in a single threaded context. Oh dear. This will also
segfault, although it takes a lot longer to do it.
--------------------------------
#! /usr/bin/guile-gnome-2
!#
(use-modules (gnome glib))
(define main-loop (g-main-loop-new #f #f))
(g-timeout-add 100
(lambda ()
(g-idle-add (lambda () (display "running ") #f))
#t))
(display "Starting main loop\n")
(g-main-loop-run main-loop)
--------------------------------
Chris
next prev parent reply other threads:[~2016-02-23 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 21:45 Potluck - thread safe event loop with await semantics Chris Vine
2016-02-22 12:01 ` Ludovic Courtès
2016-02-22 16:36 ` Marko Rauhamaa
2016-02-22 17:40 ` Chris Vine
2016-02-22 17:53 ` Thompson, David
2016-02-22 18:12 ` Chris Vine
2016-02-22 19:54 ` Christopher Allan Webber
2016-02-22 20:28 ` David Pirotte
2016-02-23 0:31 ` Chris Vine
2016-02-23 1:30 ` Chris Vine
2016-02-23 19:55 ` David Pirotte
2016-02-23 6:25 ` David Pirotte
2016-02-23 12:09 ` Chris Vine
2016-02-23 16:49 ` Chris Vine [this message]
2016-02-25 23:22 ` David Pirotte
2016-02-23 4:58 ` Chris Vine
2016-03-01 20:39 ` Amirouche Boubekki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160223164910.6a40c66c@dell.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).