Heavy resource usage when processing large queues

[John Y]

I just processed a queue of 71 files (each about 90 minutes long).
When processing was completed (apart from one file that didn't work
for some reason) and iFlicks was idle, Activity Monitor showed iFlicks
Helper to be using 702 threads, and it took about 15 seconds to switch
between applications. Force Quitting iFlicks restored performance.

Is there a resource leak somewhere? It also uses rather more real
memory than I'd like as soon as the items are queued: iFlicks had
about 550Mb real — I forget how much virtual, but it was a lot
— before even beginning to process stuff. If there's any way of
reducing this, it would really help, as I don't have a spare £150 for
extra memory right now :)

Thanks

[John Y]

On 15 Dec, 20:07, John Y <wotnosp...@gmail.com> wrote:
> I just processed a queue of 71 files (each about 90 minutes long).
> When processing was completed (apart from one file that didn't work
> for some reason) and iFlicks was idle, Activity Monitor showed iFlicks
> Helper to be using 702 threads, and it took about 15 seconds to switch
> between applications. Force Quitting iFlicks restored performance.

This happened again — 13 90-minute episodes (MST3K, for reference) and
402 threads left running after the encoding was complete. This is with
the latest beta: 1.1 (636) though it has happened with previous
releases, including stable ones.

Please could you point me to a download link for a version that
doesn't completely break my machine (a 4-core Mac Pro with 3Gb of RAM,
which should be ample for running something like this!) as I currently
can't use the program I've paid for :(

Crash logs available if you need them — let me know where to send
them…

[Jendrik Bertram]

Thanks for letting me know. I'll have a close look at this.

> --
>
> You received this message because you are subscribed to the Google Groups "iFlicks" group.
> To post to this group, send email to ifl...@googlegroups.com.
> To unsubscribe from this group, send email to iflicks+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/iflicks?hl=en.
>
>

[John Y]

On 17 Dec, 17:13, Jendrik Bertram <jend...@iflicksapp.com> wrote:
> Thanks for letting me know. I'll have a close look at this.

Thanks — one important point I forgot is that this was with the Apple
TV conversion. I'm currently running some Flatten to QuickTime exports
and the iFlicksHelper thread count seems to be remaining steady at
around 18.

Incidentally, it would be nice if we could have an option to not use
all the cores when doing format conversion; I can still use my machine
while Handbrake is doing conversions because I can tell it to leave a
few cores for me :) Preferably this would be a slider that can be
changed mid-conversion, rather than something set in Preferences, so I
can crank up the power when I leave the keyboard…

[Jendrik Bertram]

On 18.12.2009, at 12:47, John Y wrote:

> On 17 Dec, 17:13, Jendrik Bertram <jend...@iflicksapp.com> wrote:
>> Thanks for letting me know. I'll have a close look at this.
>
> Thanks — one important point I forgot is that this was with the Apple
> TV conversion. I'm currently running some Flatten to QuickTime exports
> and the iFlicksHelper thread count seems to be remaining steady at
> around 18.

I think I have fixed this. I'll release an update tomorrow which will include the fixes.

> Incidentally, it would be nice if we could have an option to not use
> all the cores when doing format conversion; I can still use my machine
> while Handbrake is doing conversions because I can tell it to leave a
> few cores for me :) Preferably this would be a slider that can be
> changed mid-conversion, rather than something set in Preferences, so I
> can crank up the power when I leave the keyboard…

Currently iFlicks is telling x264 to automatically select the number of cores used.
After the next stable version is released I'll be moving away from QuickTime to gain more flexibility. I'll see if I can add this then.

[John Y]

On 19 Dec 2009, 20:37, Jendrik Bertram <jend...@iflicksapp.com> wrote:
> I think I have fixed this. I'll release an update tomorrow which will include the fixes.

Yes, 1.2 seems to have fixed this — I was able to encode 24 MST3K
episodes and my machine was still running fine afterwards :)

Thanks!