search

turion / rhine

Haskell Functional Reactive Programming framework with type-level clocks
http://hackage.haskell.org/package/rhine
118 stars 21 forks source link

Segmentation fault when running rhine gloss examples #216

Closed madjestic closed 1 year ago

madjestic commented 1 year ago

Hey guys,

I am getting a seg.fault when running rhing gloss examples:

$ cabal run exe:rhine-gloss-gears
Up to date
Please choose between the pure (1), the pure combined (2), and the IO backend (3):
1
rhine-gloss-gears: mmap 4096 bytes at (nil): Cannot allocate memory
rhine-gloss-gears: Try specifying an address with +RTS -xm<addr> -RTS
Segmentation fault

How can I fix that?

Cheers, Vlad

turion commented 1 year ago

That's weird, I've never seen this error before. Which system do you use? How did you install everything? Can you choose options 2 or 3 in the prompt as well and see whether something changes?

madjestic commented 1 year ago

I am running a gentoo, I did all standard things, cloned the repo, cd'ed into rhine-gloss dir, cabal clean, cabal build, cabal run exe:rhine-gloss-gears.

Options 2 and 3 lead to the same result.

madjestic commented 1 year ago

Having said that, I just tried running it again and it works. That is weird indeed!

madjestic commented 1 year ago

Maybe I had exhausted RAM without noticing and allocator was failing, which is fair enough?

turion commented 1 year ago

That sounds plausible. Glad it works!

turion commented 1 year ago

Maybe it was https://discourse.haskell.org/t/facing-mmap-4096-bytes-at-nil-cannot-allocate-memory-youre-not-alone/6259

madjestic commented 1 year ago

Wagh! I will try that asap! Thanks!

On Mon, 22 May 2023 at 10:56, Manuel Bärenz @.***> wrote:

Maybe it was https://discourse.haskell.org/t/facing-mmap-4096-bytes-at-nil-cannot-allocate-memory-youre-not-alone/6259

— Reply to this email directly, view it on GitHub https://github.com/turion/rhine/issues/216#issuecomment-1556819734, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAY6LQ7JGYKNEYPHAMIQAC3XHMS5LANCNFSM6AAAAAAXYERJZU . You are receiving this because you modified the open/close state.Message ID: @.***>