Opened 7 years ago

Closed 6 months ago

Last modified 6 months ago

#14207 closed enhancement (worksforme)

Document usage of peflags on Cygwin

Reported by: jpflori Owned by: tbd
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: porting: Cygwin Keywords: cygwin, peflags, cygwin32, days101
Cc: dimpase, kcrisman Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description

By default the max heap memory available to processes is quite low on Cygwin (about 500MB) so that doctests requiring more memory than that will fail (typically doctests using PARI which doubles its memory when its not sufficient anymore, so you basically jump from 256MB to 512MB and boom).

Change History (9)

comment:1 Changed 7 years ago by jdemeyer

Why "document" and not "fix"?

comment:2 Changed 6 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:3 Changed 6 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:4 Changed 6 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:5 Changed 5 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:6 Changed 3 years ago by embray

  • Milestone changed from sage-6.4 to sage-wishlist

This isn't really an issue on Cygwin 64. It is more of an issue on 32-bit Windows where addressing is much more constrained.

comment:7 Changed 3 years ago by embray

  • Keywords cygwin32 added

comment:8 Changed 6 months ago by embray

  • Milestone changed from sage-wishlist to sage-duplicate/invalid/wontfix
  • Resolution set to worksforme
  • Status changed from new to closed

I think issues like this with PARI have been mostly fixed, or at least worked around (e.g. #20463). It might still be a problem on 32-bit Cygwin but that is not likely to ever work.

comment:9 Changed 6 months ago by slelievre

  • Keywords days101 added
Note: See TracTickets for help on using tickets.