Well, It's been happening nearly everytime I've used a large amount of duplicated data. The more values there are, the faster it seems to occur.
On Oct 7, 11:21 am, David Rutten <[EMAIL PROTECTED]> wrote: > Brent, > > How repeatable is that setup? I think I've traced the bug down to the > double-buffered graphics on the Grasshopper window. If I'm right, it > will be fixed in the next release, if not, then I'll have to keep > searching. > > -- > David Rutten > Robert McNeel & Associates > > On Oct 7, 6:14 pm, BrentWatanabe <[EMAIL PROTECTED]> wrote: > > > It only happens, perhaps obviously, when I'm dealing with a large > > point grid from a divided surface and duplicated data lists. > > > On Sep 24, 2:57 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > > Hi Brent, > > > > I see this too from time to time. It appears Grasshopper is leaking > > > resources (GDI handles or something similar). By the time the error > > > occures, it's usually too late to do anything about it. > > > This is on my list, but since it is not a clear cause/effect crash, > > > it's a hard one to find. > > > > -- > > > David Rutten > > > Robert McNeel & Associates > > > > On Sep 15, 9:48 pm, BrentWatanabe <[EMAIL PROTECTED]> wrote: > > > > > This has happened twice in the last 3 hours that Rhino freezes while > > > > using grasshopper. > > > > > It doesn't even tell me what resource rhino needs to keep running. It > > > > just pops up a dialog box with an 'OK' button that doesn't do > > > > anything. > > > > > Any thoughts?
