Re: [ANNOUNCEMENT] Uploads for 12 August

["Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>]

On 2013-08-13 09:13, Ken Brown wrote:
> Yes.  The fix was to add the following for the Cygwin build, very early
> in main():
>
>    setenv ("G_SLICE", "always-malloc", 1);
>
> I don't know why this no longer works.  Maybe Glib now does its memory
> management initialization before emacs's main() is entered.

Exactly; in glib-2.36, g_type_init has been moved to a ctor, which is 
automatically called before main(); hence, this setenv is too late now. 
  Mozilla software is also affected by this, see:

https://bugzilla.gnome.org/show_bug.cgi?id=687763
https://bugzilla.mozilla.org/show_bug.cgi?id=833117

and many others.  Firefox et al already use launcher scripts, so adding 
one more line won't be a big deal for them.

> Yaakov, is there any chance that you could patch Glib to do the
> equivalent of G_SLICE=always-malloc on Cygwin?  This isn't really an
> emacs issue.  It would affect any GTK application that provides its own
> malloc rather than using Cygwin's malloc.  (But emacs is probably the
> only such application in the distro.)

Given that the only programs which seem to be *practically* affected by 
this is our Emacs, and Firefox/Thunderbird/etc. (which we don't have 
yet), and using G_SLICE=always-malloc apparently affects performance, I 
don't think that would be an appropriate solution.

For now, I think you'll have to add a wrapper script.


Yaakov


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/