Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#2633 closed bug (invalid)

JAM vfork: Out of memory

Reported by: bbjimmy Owned by: bonefish
Priority: normal Milestone: R1
Component: Build System Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: x86

Description

jam on hrev27011 real hardware install with 448 MB of memory ....

patience... patience... found 66238 target(s) updating 8855 target(s) InitScript1 generated/haiku.image-init-vars vfork: Out of memory

Attachments (1)

screen4.png (117.2 KB ) - added by bbjimmy 16 years ago.
screenshot with activity monitor

Download all attachments as: .zip

Change History (7)

by bbjimmy, 16 years ago

Attachment: screen4.png added

screenshot with activity monitor

comment:1 by anevilyak, 16 years ago

Resolution: invalid
Status: newclosed

This won't work until swap support is complete. jam on its own needs around 550MB to do its build calculations and fork, ignoring the rest of the OS, cache, etc, as a result of which this currently won't be doable with less than ~800MB-1GB of RAM.

comment:2 by bbjimmy, 16 years ago

This may be true, but it still needs to be fixed before Alpha 1 release

comment:3 by anevilyak, 16 years ago

Yes, but it's already a well known issue with other bugs tracking it in the system. It may have been more accurate to close this as a duplicate but I couldn't find the ticket number offhand.

in reply to:  3 comment:4 by bbjimmy, 16 years ago

ticked #1972 perhaps

in reply to:  2 comment:5 by umccullough, 16 years ago

Replying to bbjimmy:

This may be true, but it still needs to be fixed before Alpha 1 release

It's already present on the proposals page (Prop #8):

http://dev.haiku-os.org/wiki/R1/Alpha1Proposals#Prop8:FinishandIncludeSwapFileSupport

Currently there is a GSoC student working on it under the mentorship of Ingo I believe.

comment:6 by anevilyak, 16 years ago

Correct and it's getting relatively close to being able to be turned on from what I've seen. Hopefully in the next few weeks.

Note: See TracTickets for help on using tickets.