I was getting the same error pretty frequently with a file I was working on (few times a day). It was a 3d grid of points, made by dividing a stack of planes. The file was relatively heavy since I had points determining the radii of spheres on these points, with a number of test conditions for distances and such. Seems to be consistent with what people are experiencing, but I would change sliders and large amounts of data would have to recalculate and no crash, but i would pan or something do something else with no real changes, and I would crash...
Don't know if this helps... Totally unrelated note, but I've been trying to figure out if there would be a way to create a varying cull pattern, governed by an input function or something. The idea would be to create the affect of a distorting grid, by only placing geometry on every Nth grid point and then shifting that series somehow... Any ideas would be appreciated. Thanks! On Oct 7, 10:49 pm, David Rutten <[EMAIL PROTECTED]> wrote: > Rob, > > that's what I'd expect if this was really a screen buffer problem. > Buffers are created and destroyed whenever the grasshopper display > changes. This obviously happens a lot and a small percentage of these > events causes crashes. We'll see if the frequency of the crash reports > diminishes after the new release. > > -- > David Rutten > Robert McNeel & Associates > > On Oct 8, 12:19 am, robhenderson <[EMAIL PROTECTED]> wrote: > > > Just to affirm the problem. I got the same error while merely panning > > around the Grasshopper window, and was, in fact dealing with data > > dup'd from subsrfs at the time. Hope that helps. > > > It's one of the more spectacular crashes I've experienced, though... > > > Keep up the great work! > > > On Oct 7, 2:17 pm, BrentWatanabe <[EMAIL PROTECTED]> wrote: > > > > Now its just straight up crashing. > > > > I'm going to try to disable sprites to see if that's the issue. > > > > On Oct 7, 12:07 pm, BrentWatanabe <[EMAIL PROTECTED]> wrote: > > > > > 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?
