Opening a local Realm over a network drive on Linux fails

[kraenhansen]

This can be reproduced from within a Linux VirtualBox by opening a local Realm file stored on the folder shared with the host OS.

Error: mmap() failed: Invalid argumentsize: 1456offset: 0
    at RealmBrowserContainer.<anonymous> (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1884)
    at step (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1667)
    at Object.next (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1648)
    at /home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1642
    at Promise (<anonymous>)
    at __awaiter (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1638)
    at RealmBrowserContainer.initializeLocalRealm (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1881)
    at RealmBrowserContainer.componentDidMount (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/build/renderer.bundle.js:1861)
    at /home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/node_modules/react-dom/lib/ReactC…:264
    at measureLifeCyclePerf (/home/zhuinden/Desktop/realm-studio-1.0.0-rc.1/resources/app.asar/node_modules/react-dom/lib/ReactC…:75)

Ideally we should probably catch this and rewrite the error message, to explain the cause.

[bmunkholm]

It's a known limitation that Realm doesn't work over a network drive. So yes this error we have seen before and could perhaps catch as a likely hint about the limitation.

[realm-probot[bot]]

Hey - looks like you forgot to add a T-* label - could you please add one (if you have access to add labels)?