View Single Post
  #10  
Old 28th February 2017
pdk42's Avatar
pdk42 pdk42 is offline
Full member
 
Join Date: Apr 2013
Location: Leamington Spa
Posts: 5,611
Thanks: 368
Thanked 1,237 Times in 927 Posts
Likes: 145
Liked 5,917 Times in 1,920 Posts
Re: Lockups with the E-M1 Mark II?

Having been a developer in real time embedded systems in my early career I can promise you all that the likely problem is software (firmware) bugs. Real time software (and your camera is a complex real time computer) has to deal with lots of hardware I/O, multiple threads, interrupts etc - and all done in a machine with limited memory and a lightweight OS. It's a much more demanding programming discipline than writing standard data processing apps on desktop or server computers.

It's very hard to test all the likely scenarios in the lab. Things like one thread or an interrupt handler dumping over a data structure that is being used by another thread (but only in certain hard-to-reproduce cases) is the sort of thing that happens. It mighty only happen one in 10000 times - and with a small test user base that might mean it's never really discovered. Sell the camera to tens of thousands of early users though and it'll happen once a day somewhere. Unfortunately, it becomes a statistical chance that it will happen and reproducing it on any one camera is very hard.

I'm sure Olympus were aware of the E-M1 crashes, as they will be of the mark II issues (although these seem at a much lower level) and I'd guess that they're running cameras with test users that have fancy logging added to drill down into the problems. They'll fix them - you'll just have to wait for a firmware update! It was that which fixed the issues with the E-M1 in its early days.
__________________
Paul
E-M1ii, Pen-F and too many lenses
flickr
Portfolio Site
Instagram
Reply With Quote