From 06bbb280c4646fb0e64866d55f78a95d5e173732 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Mon, 2 May 2016 02:26:15 -0400 Subject: java-segfault-redux: fix analysis of modern SmartDashboard --- public/java-segfault-redux.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'public/java-segfault-redux.md') 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 -- cgit v1.2.3