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.

Sign up for GitHub

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

Jump to bottom

Document usage of peflags on Cygwin #14207

Closed
jpflori opened this issue Mar 1, 2013 · 5 comments
Closed

Document usage of peflags on Cygwin #14207

jpflori opened this issue Mar 1, 2013 · 5 comments
Labels
c: porting: cygwin r: worksforme t: enhancement

Comments

@jpflori
Copy link

jpflori commented Mar 1, 2013

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).

CC: @dimpase @kcrisman

Component: porting: Cygwin

Keywords: peflags, cygwin32, days101

Issue created by migration from https://trac.sagemath.org/ticket/14207
@jpflori jpflori added this to the sage-5.11 milestone Mar 1, 2013
@jdemeyer
Copy link

jdemeyer commented Mar 6, 2013

comment:1

Why "document" and not "fix"?

@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@embray
Copy link
Contributor

embray commented Apr 13, 2017

comment:6

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.

@embray embray removed this from the sage-6.4 milestone Apr 13, 2017
@embray
Copy link
Contributor

embray commented Apr 18, 2017

Changed keywords from cygwin peflags to peflags, cygwin32

@embray
Copy link
Contributor

embray commented Jun 15, 2019

comment:8

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.

@embray embray closed this as completed Jun 15, 2019
@slel
Copy link
Member

slel commented Jun 16, 2019

Changed keywords from peflags, cygwin32 to peflags, cygwin32, days101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: porting: cygwin r: worksforme t: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@embray @jpflori @slel @jdemeyer