hi chrysn, i have an extremely powerful machine with 16gb of 2400mhz DDR4 RAM, 8-core i7 and a 2500mbyte/sec SSD. speed is *not* a problem :) a simple model easily gives a framerate of appx 30fps.
however it is working really rather hard: i had openscad run with a window @ 1940 x 1400 and was rotating the object round with the mouse for just over 30 seconds, possibly longer. one core jumped to a frequency of 2.27ghz and CPU usage was 50%. i've just tried this again but could not reproduce it. it *really* is a bit of a bitch i'm afraid. two circumstances where it's *definitely* reproducible: * current version of chrome browser when you're using the web-based facebook "chat". * resizing glxgears under fvwm2 (this one is 100%) this latter causes fvwm2 to show a wire-frame only, during which time the race condition is triggered instantly. other circumstances are much much harder to reproduce, which is why it's been well over a year, now, and this bug is still outstanding (wherever it is). sorry i couldn't give better news! l. On 3/28/17, chrysn <chr...@fsfe.org> wrote: > Hi, > > On Tue, Mar 28, 2017 at 01:56:21PM +0100, lkcl wrote: >> the issue appears to be that a race condition causes a frame to be >> dropped. however once there is only one frame dropped, *all* >> subsequent frames stop from that point onwards. > > that is a tricky one. > > I've tried to reproduce the issue with octave-gui as described in > #848895 (even under full CPU load as "helped" with the chromium > version), but it did not trigger a lockup on my machine. > > Are there any other known ways to trigger this (to find out which > machines are affected at all), or to trigger this in OpenSCAD? > > Best regards > chrysn >
