[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #26 from Bawolff (Brian Wolff) bawolff...@gmail.com --- (In reply to comment #22) Patch in https://gerrit.wikimedia.org/r/#/c/57478/ to bump from 100MB to 400MB got merged. Anything left here to do, or can this ticket be closed

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Jan Gerber jger...@wikimedia.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #24 from Jan Gerber jger...@wikimedia.org --- created https://bugzilla.wikimedia.org/show_bug.cgi?id=47311 to track use of vipsthumbnail (and update to 7.32.2) -- You are receiving this mail because: You are on the CC list for the

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #23 from John Cupitt jcup...@gmail.com --- (In reply to comment #22) Anything left here to do, or can this ticket be closed as FIXED? I'm the vips maintainer. As it stands, the VipsScalar plugin will cause a lot of disc traffic.

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #22 from Andre Klapper aklap...@wikimedia.org --- Patch in https://gerrit.wikimedia.org/r/#/c/57478/ to bump from 100MB to 400MB got merged. Anything left here to do, or can this ticket be closed as FIXED? -- You are receiving

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #21 from Gerrit Notification Bot gerritad...@wikimedia.org --- https://gerrit.wikimedia.org/r/57478 (Gerrit Change I8ab3375c709ddb495eaf0e0cc5d90d6f5fe7110b) | change APPROVED and MERGED [by Tim Starling] -- You are receiving this

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #18 from Jan Gerber jger...@wikimedia.org --- @John, looking at this right now, and I have some issues with vips-7.28.5: vipsthumbnail insists on writing the output in the folder of the input: vipsthumbnail

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #19 from John Cupitt jcup...@gmail.com --- @Jan, there was a bug in vipsthumbnail, it only allowed relative paths in -o. This was fixed in 7.32, the current stable version. Could you try that? I'll look into the im_shrink() error.

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #20 from John Cupitt jcup...@gmail.com --- Here's the issue on the vipsthumbnail absolute pathname problem, for reference. It includes a patch, though of course it'd be better to update to current stable.

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Rob Lanphier ro...@wikimedia.org changed: What|Removed |Added CC||ro...@wikimedia.org

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #16 from John Cupitt jcup...@gmail.com --- Good news, please don't hesitate to mail me if there's any way I can help. Bryan's excellent extension needs revising to use vipsthumbnail. As it stands VipsScalar will not be able to make

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #17 from John Cupitt jcup...@gmail.com --- A less intrusive change would be to append :seq to the PNG filenames in Bryan's VipsScalar extension. This will turn on the streaming mode and get memuse and disc use down. It would be

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #14 from John Cupitt jcup...@gmail.com --- A new vips is out, so I thought I'd update the benchmark again with the latest version of each package. This time I've used my laptop. This has an i5-3210M at 2.5 GHz and 6gb of RAM. On

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Tim Starling tstarl...@wikimedia.org changed: What|Removed |Added Blocks||28135 -- You

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #13 from Bryan Tong Minh bryan.tongm...@gmail.com --- Tim, would you have time to look into this again? It looks like that with vips-7.28, vips becomes useful again at least for our PNG problem? I'd prefer to continue on the vips

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #12 from John Cupitt jcup...@gmail.com 2012-09-28 11:51:19 UTC --- I've redone all the benchmarks with the latest version of each package. Thank you for the link to your interesting project Derrick. Summary: program | real

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Derrick Coetzee d...@moonflare.com changed: What|Removed |Added CC||d...@moonflare.com

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #9 from John Cupitt jcup...@gmail.com 2012-03-19 12:28:17 UTC --- vips-7.28 is now officially out and includes sequential mode read. In this mode, vips streams the image from the file format read library, caching just a few hundred

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #10 from John Cupitt jcup...@gmail.com 2012-03-19 14:20:17 UTC --- I've just realised that the -thumbnail option for convert is doing very crude subsampling, hence the horrible aliasing in the shrunk image. You need to use -resize

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 John Cupitt jcup...@gmail.com changed: What|Removed |Added CC||jcup...@gmail.com ---

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #5 from Bryan Tong Minh bryan.tongm...@gmail.com 2011-12-05 19:54:08 UTC --- (In reply to comment #4) For PNGs, i.e. the whole point of this project, we seem to be pretty much screwed. I haven't looked into the details of when it

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Derk-Jan Hartman hart...@videolan.org changed: What|Removed |Added CC|

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #7 from Tim Starling tstarl...@wikimedia.org 2011-12-06 00:15:34 UTC --- (In reply to comment #5) The whole problem is that the PNG reader is WIO instead of PIO right? I'm wondering whether it is easier to write a PIO PNG reader

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #4 from Tim Starling tstarl...@wikimedia.org 2011-12-05 04:21:16 UTC --- Hmmm, this is a pretty large error on my part. VIPS is not doing any low memory magic when reading JPEG or PNG source images. VIPS is writing out an

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Mark A. Hershberger m...@everybody.org changed: What|Removed |Added Priority|Unprioritized |Normal

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 Tim Starling tstarl...@wikimedia.org changed: What|Removed |Added Summary|VIPS test: VIPS fails on|VIPS out of

[Bug 32721] VIPS out of memory on large (100 Mpx) non-progressive JPEG

https://bugzilla.wikimedia.org/show_bug.cgi?id=32721 --- Comment #3 from Bryan Tong Minh bryan.tongm...@gmail.com 2011-11-30 10:48:59 UTC --- It looks like increasing the sharpening to 1.2 helps quite a bit for the small image without bilinear scaling. -- Configure bugmail: