# EyeLink crashes MWServer

**URL:** <https://mworks.discourse.group/t/eyelink-crashes-mwserver/909>\
**Category:** Support\
**Created:** [August 28, 2023, 4:15pm UTC](https://mworks.discourse.group/t/eyelink-crashes-mwserver/909 "2023-08-28T16:15:54Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)\
**Post date:** [August 29, 2023, 4:19pm UTC](https://mworks.discourse.group/t/eyelink-crashes-mwserver/909/7 "2023-08-29T16:19:41Z")

</div>

Hi Yoon,

I figured out what’s happening.

A change made in MWorks 0.12 caused creation of the EyeLink data file to fail. While that should just produce a warning from MWorks, an undocumented change to the EyeLink API causes the failure to lead to a MWServer crash. I don’t know when the latter change happened, but it’s present in the previous release of the EyeLink drivers.

The reason I saw a crash in MWorks 0.11 while you didn’t is that I was triggering a different EyeLink error – specifically, I was attempting to connect to a non-existent tracker. I think this means that, even with 0.11, _any_ EyeLink error is going to crash MWServer. Hopefully you won’t hit any such errors, but just be aware.

For the moment, sticking with MWorks 0.11 is the right move. I will get fixes for both issues into the nightly build soon. This probably also warrants a 0.12.2 release.

Cheers,  
Chris

---

_[View the full topic](https://mworks.discourse.group/t/eyelink-crashes-mwserver/909)._