[#11073] segfault printing instruction sequence for iterator — <noreply@...>

Bugs item #10527, was opened at 2007-05-02 14:42

14 messages 2007/05/02
[#11142] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Nobuyoshi Nakada <nobu@...> 2007/05/10

Hi,

[#11188] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Paul Brannan <pbrannan@...> 2007/05/16

On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:

[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>

Hi all.

17 messages 2007/05/25

Re: $2000 USD Reward for help fixing Segmentation Fault in GC

From: "sur max" <sur.max@...>
Date: 2007-05-31 11:48:12 UTC
List: ruby-core #11375
Hey Meinrad,

I never came across this fact earlier that WeakRef usage can lead to the
performance loss..
It will be great if you can provide some links justifying the same.

Thanks

--
Sur Max
http://expressica.com

On 5/31/07, Meinrad Recheis <meinrad.recheis@gmail.com> wrote:
>
> On 5/31/07, sur max <sur.max@gmail.com> wrote:
> > Hi Brent,
> >
> > Although i can not anticipate the code structure, still suggesting...
> please
> > ignore if you have already tried that out!
> >
> > using WekRef library, a lots of memory management problems can be
> solved...
> > i have implemented it in various cases and that worked out well.
>
> be warned, though, that using weakref extensively can result in
> extreme performance loss. it is really very slow!
>
> -- henon
>
>


-- 
sur

In This Thread