[BUG] Crash on large JSON responses

[ardakazanci]

What happened?

Experiencing crashes in the Flocon app when parsing large JSON responses.

Once we fix this, Flocon will be stronger and more scalable.

Keep on rockin !

Version

1.2.0

What platform are you seeing the problem on?

Desktop

Relevant log output

[florent37]

hi @ardakazanci , can you give me more context on this ?

what are the steps to reproduce,
and if possible give me by pastebin the json you are using

[ardakazanci]

Unfortunately, I cannot share the JSON. However, I am getting such a crash from a very large JSON dataset. I get it the moment I click on the relevant service on the listing screen.

[florent37]

don't worry about the json

then to be sure, you got it on the list of calls, when you are receiving a very big json ?

or when you are clicking on an item of the list to display the right pannel ? (here the body is displayed)

[florent37]

I can ask chatGpt to generate a very long json to try

[ardakazanci]

I'm already getting an error when I try to view it. 🥲 Sample -> 100 mb .json file

[florent37]

hum, I'm using a websocket for exchanges between the android client and the desktop, it's limited to 16mb something like this, not sure it's possible for flocon-destktop to be aware of 100mb calls

[florent37]

I think it's a limitation of Strings also, not possible to represent a 100mb content into a String

[ardakazanci]

A similar problem exists in Flipper.

[florent37]

any idea how to fix it or prevent it ?

I'm storing items into a room database
and then extracting them into a data class, for sure it's not possible to represent this on a String

[ardakazanci]

cacheDir or room. String will be difficult, as you said.

[florent37]

fixed, now for large json it will hide then, and you buttons to :

• 1 open externally (ex: in sublime text)
• 2 open it in the app