summaryrefslogtreecommitdiff
path: root/public/java-segfault-redux.md
diff options
context:
space:
mode:
Diffstat (limited to 'public/java-segfault-redux.md')
-rw-r--r--public/java-segfault-redux.md12
1 files changed, 10 insertions, 2 deletions
diff --git a/public/java-segfault-redux.md b/public/java-segfault-redux.md
index 85e92eb..e05e9d8 100644
--- a/public/java-segfault-redux.md
+++ b/public/java-segfault-redux.md
@@ -216,8 +216,16 @@ longer has this bug, and it's not using my workaround. So, how did
the WPILib developers fix it?
Well, the code now lives [in git at collab.net][git], so I decided to
-take a look. They put a mutex around all accesses to `image`, which
-should have been the obvious solution to me.
+take a look.
+
+The stripped out WPIJavaCV from the main video feed widget, and now
+use a purely Java implementation of MPJPEG streaming.
+
+However, the old video feed widget is still available as an extension
+(so that you can still do cool things with `processImage`), and it
+also no longer has this bug. Their fix was to put a mutex around all
+accesses to `image`, which should have been the obvious solution to
+me.
[original]: ./java-segfault.html
[HN]: https://news.ycombinator.com/item?id=9283571