Re: [fossil-users] Unused artifact view

On 1/22/18, bytevolc...@safe-mail.net wrote: > In rebuild.c (commit 1a95af721e467a6e3321c1557c4f0cdfa353ef4a): > > Ln 168: > > db_multi_exec( > "CREATE VIEW IF NOT EXISTS " > " repository.artifact(rid,rcvid,size,atype,srcid,hash,content) AS " > "

Re: [fossil-users] Bug Report: Fossil 2.3 runs out of Memory During Check-in

[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

[fossil-users] Unused artifact view

In rebuild.c (commit 1a95af721e467a6e3321c1557c4f0cdfa353ef4a): Ln 168: db_multi_exec( "CREATE VIEW IF NOT EXISTS " " repository.artifact(rid,rcvid,size,atype,srcid,hash,content) AS " "SELECT blob.rid,rcvid,size,1,srcid,uuid,content" " FROM blob LEFT JOIN delta ON

Re: [fossil-users] Bug Report: Fossil 2.3 runs out of Memory During Check-in

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

Re: [fossil-users] Bug Report: Fossil 2.3 runs out of Memory During Check-in

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

[fossil-users] Bug Report: Fossil 2.3 runs out of Memory During Check-in

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