>>> I've seen your HEAD changes, I'm on 2dd25909da and the > I'm not sure if this is related, but I've not followed the process for > whole time, but seen that during the meta-data rebuild it quite grows > in memory. While being at 37% of rebuild it was already eating around > 330 MB of RAM. So my idea is, the crash above may also mean that whole > memory is consumed (this is 32bit binary). I will retest the same and > see how memory consumption develops.
Retesting shows that fossil consumes about 640 MB of RAM at the time of crash. ulimit should not limit it too: karel@silence:/tmp/fossil-test$ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 10 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 29995 virtual memory (kbytes, -v) unlimited anyway, this is still 2dd25909da on Solaris. Also please note that I've checked RAM consumption every 10 seconds and record that so if there is a fast spike it still may slip through it. On OpenBSD I do have 09d3e7ebf0 but this is still working on git->fossil import. I'll retest clone crash issue there too once done. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
