[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-smalltalk] Re: [bug] CPU usage is high when there is an exception

From: Paolo Bonzini
Subject: [Help-smalltalk] Re: [bug] CPU usage is high when there is an exception
Date: Wed, 18 Nov 2009 04:02:24 -0700

Issue status update for Post a follow up:

Project:      GNU Smalltalk
Version:      <none>
Component:    VisualGST
Category:     bug reports
Priority:     critical
Assigned to:  Unassigned
Reported by:  MrGwen
Updated by:   bonzinip
Status:       active

This would fix it:

diff --git a/packages/gtk/ b/packages/gtk/
index 6a2d2fc..6097775 100644
--- a/packages/gtk/
+++ b/packages/gtk/
@@ -502,7 +502,7 @@ Gtk class extend [
        GTK.Gtk main: sem.
        sem wait.
- [GTK.Gtk mainIterationDo: false.
+        [GTK.Gtk mainIterationDo: true.
GTK.Gtk shouldQuit] whileFalse: [Processor yield]

but I have to check the impact on simulation speed (e.g. does moving
the mouse increase the speed of simulation? that would be bad!).  To
fix it properly, the glib event loop should be hacked up to run the
event loop together with Smalltalk code:

   *  Place the main loop at high priority and make it do something
like this: 1) use g_main_context_set_poll_func and in the poll function
set up SIGIO notification for the file descriptors, call
g_main_context_pending to get this poll function called; 2) wait on a
semaphore to be triggered by the SIGIO notifications; 3) revert to the
default poll function and call g_main_context_iteration in non-blocking
   *  Besides this, in sysdep/win32/events.c use
MsgWaitForSingleObjects instead of WaitForSingleObject

reply via email to

[Prev in Thread] Current Thread [Next in Thread]