Re: nxclient (NoMachine) after recent Leopard X package updates
Re: nxclient (NoMachine) after recent Leopard X package updates
- Subject: Re: nxclient (NoMachine) after recent Leopard X package updates
- From: "Mark J. Reed" <email@hidden>
- Date: Fri, 14 Dec 2007 18:27:19 -0500
If I may interject a dumb question born of not being familiar with the
codebase - is that a baby floating downstream with your bathwater?
What is wrong with alloca? Is it a buggy implementation? Or was it
being used in places where it shouldn't be because the mem needs to
stick around after the allocating function returns? Or something else?
Just curious...
On 12/14/07, Jeremy Huddleston <email@hidden> wrote:
>
> On Dec 14, 2007, at 10:37, Paul Ingram wrote:
>
> > I've had at least a dozen X11 crashes using NX with the 1.2a* builds
> > of Xquartz. Sometimes it would be days between crashes, sometimes
> > only minutes. It always seemed to occur when switching focus and
> > xemacs was often involved.
> >
> > Each time I this happened I needed to restart my computer before NX
> > would work again.
> >
> > On the upside, the notorious yellow cursor problem was fixed. That's
> > almost worth taking the crashes for.
> >
> > I've upgraded to the new 1.2.1 build and haven't seen a crash in
> > about 6 hours of use so it's probably still too early to be certain
> > that the problem is fixed.
>
> You probably mean 2.1.1.
>
> I believe a good handful of the crashes were caused by alloca()
> related issues. So 2.1.1 should see a nice stability improvement
> because we are now not using alloca().
>
> --Jeremy
--
Mark J. Reed <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden