search

bright-fish / node-ui-automation

MIT License
2 stars 1 forks source link

Calling `getNextSiblingElement` when there isn't another sibling causes the process to crash #1

Closed jakecyr closed 2 years ago

jakecyr commented 3 years ago

Process crashes with error 77 Segmentation fault

bright-fish commented 2 years ago

Looking into this to see if it is still an issue.

bright-fish commented 2 years ago

This must have been on a previous version that had a bug. In the current version it returns null, which is expected, and to follow through if you invoke getNextSiblingElement with the null value it errors with Cannot convert undefined or null to object. I think this is not an issue with the current version.