> So after about 8 hours and 3 restarts, your tarball finally downloaded… and
> inside, I found another 17 TB tarball!
GB, not TB.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Jan 27, 2018, at 12:20 AM, Martin Vahi wrote:
>
> https://temporary.softf1.com/2018/bugs/2018_01_26_Fossil_out_of_RAM_bug_test_case_t1.tar.xz
So after about 8 hours and 3 restarts, your tarball finally downloaded… and
inside, I found another 17 TB tarball!
That
On Jan 27, 2018, at 3:09 AM, Stephan Beal wrote:
>
> Simply reading that file for insertion into the db requires 1x its size.
Obviously this *could* be changed, so that BLOBs stream into and out of the
SQLite DB in chunks. That gets us back to motivation: why spend the
On Sat, Jan 27, 2018 at 8:20 AM, Martin Vahi wrote:
> About 5GiB of it is the Fossil repository file and
> about 17GiB of it is a tar-file with about 140k files that
> the test tries to insert to the fossil repository.
>
i'm gonna go ahead and say it because every else
> Date: Mon, 22 Jan 2018 09:06:10 -0500
> From: Richard Hipp
> On 1/22/18, Martin Vahi wrote:
>>
>> citation--start---
>> Fossil internal error: out of memory
>> citation--end-
>>
>> It happened during the execution of the
>>
>>
[Default] On Mon, 22 Jan 2018 13:54:00 -0700, Warren Young
wrote:
> Fossil makes some reasonable assumptions about its working
> environment: individual file sizes are a small fraction of
> available VM, the entire repository probably fits into VM,
> and if not, then it can
On Jan 22, 2018, at 6:44 AM, Martin Vahi wrote:
>
> Fossil had an opportunity to allocate
> at least 1GiB of RAM
There are cases where Fossil needs 2-3x the size of an object to operate.
For example, my understanding of the way Fossil does the diff operation is that
On 1/22/18, Martin Vahi wrote:
>
> citation--start---
> Fossil internal error: out of memory
> citation--end-
>
> It happened during the execution of the
>
> fossil ci
Do you have a test case that we can use for debugging?
--
D. Richard Hipp
citation--start---
Fossil internal error: out of memory
citation--end-
It happened during the execution of the
fossil ci
Given that the Fossil had an opportunity to allocate
at least 1GiB of RAM without running out of RAM,
the issue must have something to do with
9 matches
Mail list logo