Big Sur Segmentation Fault when retrieving window title

[dwighthouse]

Version Node v17.0.1 nut.js v2.0.1

Short overview Trying to retrieve title of any window results in Seg Fault and no other information, program ends immediately.

Issue occurs on

• [ ] Virtual machine
• [ ] Docker container
• [x] Dev/Host system

Detailed error description Seg fault is occurring on Big Sur any time I attempt to find a window title, either through getWindows or getActiveWindow.

Steps to reproduce error Run this script:

import { getActiveWindow } from '@nut-tree/nut-js';

(async () => {
    const window = await getActiveWindow();
    const title = await window.title;
    console.log(title);
})();

Expected Result: Terminal

Actual Result: zsh: segmentation fault node index.js

[s1hofmann]

Observation: Reproducibly segfaults when executed in Terminal.app, no matter which window is currently active. Runs fine in e.g. iTerm, though

Edit: This was due to my setup. Reproducibly segfaults in any terminal

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[s1hofmann]

Still open

[mwarger]

I also see this error regardless of the terminal used. Tried in iTerm and got the same error.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[jzombie]

Can confirm this issue is happening on Mac M1 using Terminal and iTerm for accessing window titles.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.

[sublimator]

Crashing for me too

[s1hofmann]

Status update:

This issue had me banging my head for several months now. I might have finally tracked down the root cause 💪

Still WIP

[sublimator]

Great to hear. Liking the lib so far.

[s1hofmann]

Root cause: Reading the kCGWindowName property requires an application to be given Screen Recording permissions. If this is not the case, it'll just return nil which caused the segfault.

Fixed in release 2.3.0 that just went live.

[sublimator]

Yay!