Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tfragment_alloc.nim (which allocates 4GB) often makes appveyor fail with out of memory #8509

Closed
timotheecour opened this issue Aug 1, 2018 · 0 comments

Comments

@timotheecour
Copy link
Member

timotheecour commented Aug 1, 2018

@Araq this commit 6d4107b allocates 4GB

  when defined(cpu64):
    # bug #7120
    var x = alloc(((1 shl 29) - 4) * 8)
    dealloc x

and often causes appveyor to fail with out of memory, eg:
https://ci.appveyor.com/project/Araq/nim/build/5348

PASS: tunhandledexc.nim C                                          (1.73437524 secs)
PASS: twrongexc.nim C                                              (1.63440394 secs)
tests\testament\tester.exe "--nim:compiler\nim " cat fragmentation
FAIL: tfragment_alloc.nim C
Test "tests\fragmentation\tfragment_alloc.nim" in category "fragmentation"
Failure: reExitcodesDiffer
Expected:
exitcode: 0
Gotten:
exitcode: 1
Output:
out of memory
SKIP: tfragment_gc.nim C
FAILURE! total: 2 passed: 0 skipped: 1

(I've seen this flaky test a number of times)

Should we disable this test?

NOTE to self:
((1 shl 29) - 4) * 8 is 4GB

@timotheecour timotheecour changed the title tfragment_alloc.nim (which allocates 2GB?) often crashes appveyor tfragment_alloc.nim (which allocates 4GB) often crashes appveyor Aug 1, 2018
@timotheecour timotheecour changed the title tfragment_alloc.nim (which allocates 4GB) often crashes appveyor tfragment_alloc.nim (which allocates 4GB) often makes appveyor fail with out of memory Aug 1, 2018
timotheecour added a commit to timotheecour/Nim that referenced this issue Aug 1, 2018
@Araq Araq closed this as completed in 9a390d6 Aug 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant