search

project-beholder / beholder-detection

MIT License
7 stars 0 forks source link

Marker.present doesn't persist #4

Open zepumph opened 3 years ago

zepumph commented 3 years ago

While using my demo this morning on Google chrome (Version 88.0.4324.190 (Official Build) (64-bit)), I found that given a "fresh" set of parameters, I could get the present markers to be logged, but then the next frame they would not be marked as present. This was the case even though the video screen showed the detected markers highlighted on the screen (see below). Marker.present would only be correct when I altered a parameter, and then again only for a single frame.

image

Demo I was using (I experienced with with older versions of beholder also.)

```html ```
zepumph commented 3 years ago

Found with beholder 1.1.10

zepumph commented 3 years ago

@Petroochio and I found that this seems to be based on CPU power. When we throttle the tab in chrome dev tools, we can consistently reproduce this error. We can in fact make it so that the markers never appear present.