IOS - IOException - too many files open about ffimageloading

[molinch]

Difficult to say without reproduce sample. Could upload something or pieces of your code?
If you prefer to send via email it's also fine

[bertbeck]

I'll put together a sample and email it

Does the code limit the number of simultaneous transfers ? Is there a way
to set the max # ?

thanks

Bert

On Wed, Oct 14, 2015 at 12:45 PM, Fabien Molinet [email protected]
wrote:

Difficult to say without reproduce sample. Could upload something or
pieces of your code?
If you prefer to send via email it's also fine

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[molinch]

Max number of concurrent transfers is limited by number of physical cores. So it should not be a lot in fact. It's quite strange that you get this, I'm wondering if it's not a Xamarin iOS issue under the hood.

The sample will definitely help: you can email it at fabien.molinet AT gmail.com

[molinch]

Do you have SGen generational garbage collector turned on?
(Project properties, iOS Build, Advanced)

Btw I tried to debug it with "XCode Instruments> File Activity" but I don't see any file descriptor leak on my side.

[molinch]

Any news Bert?

[bertbeck]

Hi Fabien,

Not yet - I've been overly busy trying to get a beta out. I'll have more
time on this in the next few days.

It fails once in a while but not all the time.

I'll try to get you something over the weekend.

Btw - in chatting with another developer - an idea popped up -

Allow batching of image loads

This would require the developer to create a special backend web
method/service

Basically - in your cache manager - batch up requests to common urls and
make one call passing the list of images in user specified batch amounts
(10,20,50,...)

And have them send a multipart response with the images requested

Would ave a lot of tcp connections (or do you keep alive ?)

Bert

On Fri, Oct 16, 2015 at 1:38 PM, Fabien Molinet [email protected]
wrote:

Any news Bert?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[molinch]

@bertbeck Batching of image load is interesting but really tightly coupled to the backend so it would not fit in this lib. It could be transparent for you if you were using HTTP2 for example with a HttpHandler that supports it (HTTP2 offers multiplexing).

If you want to have more advanced features like connection pooling/connection reuse I think that NSUrlSession offers these on iOS but I don't know if anything should be configured. ModernHttpClient relies on NSUrlSession, you just need to pass the HttpClient in ImageService.Initialize. Be aware of these 2 bugs though: #49

It would be very nice if you could deliver a small repro though :)

[bertbeck]

Hi Fabien,

The problem may be better - I updated Xamarin tools and to XCode 6.4, and
things seems to be better. I've been working on another part of the project

• will return to messaging (where this problem comes up) this week and I
  will send you a small repo when I can.

I'll have more input and may try image batching down the road.

thanks

Bert

On Sun, Oct 25, 2015 at 4:16 PM, Fabien Molinet [email protected]
wrote:

@bertbeck https://github.com/bertbeck Batching of image load is
interesting but really tightly coupled to the backend so it would not fit
in this lib. It could be transparent for you if you were using HTTP2 for
example with a HttpHandler that supports it (HTTP2 offers multiplexing).

If you want to have more advanced features like connection
pooling/connection reuse I think that NSUrlSession offers these on iOS but
I don't know if anything should be configured. ModernHttpClient relies on
NSUrlSession, you just need to pass the HttpClient in
ImageService.Initialize. Be aware of these 2 bugs though: #49
#49

It would be very nice if you could deliver a small repro though :)

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[molinch]

Any news @bertbeck ?

[bertbeck]

Hi Fabien,

The problem seems to have disappeared. Xamarin updated its tools (maybe
also updated mono) and I have not seen the problem lately.

If it re-surfaces - I'll let you know.

We'll probably do a lot more testing after January - the project has been
on hold.

Bert

On Sun, Nov 29, 2015 at 4:13 PM, Fabien Molinet [email protected]
wrote:

Any news @bertbeck https://github.com/bertbeck ?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[daniel-luberda]

@molinch It may be something related to this: #80 (comment)

[daniel-luberda]

Hi @bertbeck. There were some changes in 2.0.0-alpha4 - now, FFImageLoading queues file saving operations, so it shouldn't throw "too many open files" exceptions. If you still experience this bug - feel free to reopen the issue.

[bertbeck]

thanks

On Tue, Dec 8, 2015 at 2:54 PM, Daniel Luberda [email protected]
wrote:

Closed #61 #61.

—
Reply to this email directly or view it on GitHub
#61 (comment).