Page 1 of 1
Frequent crashing: Uncaught TypeError ‘OptionValue’
Posted: Sat Aug 21, 2021 8:02 pm
by adamduff
Hi, please can someone help - I’ve not been able to find anyone else reporting this problem, but my UI3 instance (in Chrome) keeps crashing with this error message. I can resolve with refresh (or closing/reloading Chrome), but it just keeps coming back:
An unexpected error has occurred in /ui3.GRN (v 161 / 5.4.9.18)…
…Uncaught TypeError: Cannot read property ‘optionValue’ of null at
http://host name/ui3/ui3.js?v=161-5.4.9.18 [10758:53]…
Full screenshot attached…
Any ideas/help? (thanks!)
Re: Frequent crashing: Uncaught TypeError ‘OptionValue’
Posted: Sun Aug 22, 2021 9:48 am
by TimG
Hi,
Two thoughts:
1. Can you try Ui3 on a different browser on the same pc ?
2. Can you try UI3 on a different pc ?
I believe Ui3 was written by forum member bp2008, so you could try to PM the author directly, otherwise, send a message to Support.
Re: Frequent crashing: Uncaught TypeError ‘OptionValue’
Posted: Mon Aug 23, 2021 7:21 pm
by adamduff
Thanks, I tried Edge on the same PC and so far so good - no more crashes
(interestingly I tried Chrome on another PC on same local network and cannot get it to reproduce the same problem too, so it seems to be that combination of browser/PC that has the issue - weird - but I have a suitable workaround, so appreciate it!)
Re: Frequent crashing: Uncaught TypeError ‘OptionValue’
Posted: Thu Aug 26, 2021 6:56 pm
by adamduff
Ah, it took a little while, but now getting the same message via Edge - so it's not browser specific. I'm now trying to see if I can replicate this issue on another PC (if I leave it long enough), so let's see if it's my machine...
- Capture.jpg (255.24 KiB) Viewed 1999 times
…EDIT: now seeing this on another PC too, so it’s not browser or PC specific:
- Capture 2.jpg (88.22 KiB) Viewed 1984 times
Re: Frequent crashing: Uncaught TypeError ‘OptionValue’
Posted: Sun Sep 05, 2021 9:15 am
by adamduff
Just in case anyone else see's this issue - I contacted the Blue Iris support team over this and they were great. I was asked to install a UI3 update to provide better debugging to help track the issue (which it did). Some immediate improvements were made to UI3, but some updates were also required to BI itself too - so hopefully this issue is fully resolved (or will be soon). Thanks!