Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mhwlng]

In an upcoming build, the MCWS/v1/Browse/Image function should behave more sanely, and directly return a high-resolution artwork, and not only on the second call (or a bit randomly at that).
Hendrik

after a few of these high resolution MCWS calls, media center now crashes :

Code: [Select]

http://xxxxx:52199/MCWS/v1/Browse/Image?ID=1021&Width=680&Height=1000&Format=jpg&Token=lTiqjseX
It looks like there is no crash at a lower resolution :

Code: [Select]

http://xxxxx:52199/MCWS/v1/Browse/Image?ID=1006&Width=320&Height=476&Format=jpg&Token=lTiqjseX

[Hendrik]

after a few of these high resolution MCWS calls, media center now crashes :

Define "a few"? A few hundred, a few thousand?
It caches the thumbnails in memory, did you maybe pay attention to MCs memory usage when it happens?

It does reclaim the memory again eventually though, clearing the cache.
I wonder how many you really have to query in a short period for memory to be an issue.

At least I managed to grab all my Series images (around 100) on one page and not run into trouble.

[mhwlng]

the MCWS calls come from a web page with about 60 TV show posters on it.
So, potentially, 60 MCWS calls could be made at the same time.
The Media Center PC has 16GB RAM so it is unlikely that it runs out of memory.
I've seen Media Center crash after downloading 5 pictures or 20 pictures. It's not consistent.

[Hendrik]

I tried the same setup, but no luck reproducing, can you post or send a crash log? including a crash dump would be great (it should by default be in the log zip it generates)

[mhwlng]

I hope this helps

>>log<<

When I first switched on logging, media center didn't crash but just hung.
the second time it crashed (I think after 4 images), I restarted media center and created this log.

[Hendrik]

Thanks, that helped. I think I know why it crashed, just need to figure out the best way to fix it.

[Hendrik]

There should be a fix coming in build 122.

[mhwlng]

Thank You!