PS5 - LibAsync Failures

FlopsyPrince
FlopsyPrince
✭✭✭✭✭
✭✭✭
Is anyone else getting frequent LibAsync errors when moving to a new area? Can I ignore these since I am fine with timed processes waiting a bit longer. Or do I need to force a UI reload each time?
PC
PS4/PS5
  • Dack_Janiels
    Dack_Janiels
    ✭✭✭
    Posting the error with advanced info enabled would be helpful to see what the cause is.
  • FlopsyPrince
    FlopsyPrince
    ✭✭✭✭✭
    ✭✭✭
    Posting the error with advanced info enabled would be helpful to see what the cause is.

    This is the most common error. I am not sure if it is identical each time, but it has the same "set" of lines.

    e44yixlsrbx2.jpg

    PC
    PS4/PS5
  • LootAllTheStuff
    LootAllTheStuff
    ✭✭✭✭✭
    I'm not familiar with mods, but looking at that library's ESOUI page suggests something using the library is trying to do too much at zone load in. What mods do you have running that list LibAsync as a dependency, and what are they for?
  • freespirit
    freespirit
    ✭✭✭✭✭
    ✭✭✭
    I get that error or similar, fairly often on PC too, I believe in my case it is related to the collecting of sales data.

    Libasync is a dependency of Master Merchant, if I disable MM the error stops occuring, tbh I've given up trying to fix it and now just dismiss the error.
    When people say to me........
    "You're going to regret that in the morning"
    I sleep until midday cos I'm a problem solver!
  • FlopsyPrince
    FlopsyPrince
    ✭✭✭✭✭
    ✭✭✭
    freespirit wrote: »
    I get that error or similar, fairly often on PC too, I believe in my case it is related to the collecting of sales data.

    Libasync is a dependency of Master Merchant, if I disable MM the error stops occuring, tbh I've given up trying to fix it and now just dismiss the error.

    It comes up when I zone into someplace, not when I look at any kind of vendor. I am only using the TSC addon, since this is the PS5.

    I find I seem to get away with ignoring it, but I would expect I am not the only one facing this.

    Though ZOS may be killing addons now on the PS5 with this DMCA tomfoolery, but this seems independent.
    PC
    PS4/PS5
  • freespirit
    freespirit
    ✭✭✭✭✭
    ✭✭✭
    Oh my pop up is random too, not related to vendors at all.

    I have only managed to pin it down to when data is being processed in the background, often I see some read out in chat but not always and the error doesn't appear consistently.

    I've checked the addons I'm currently using and only MM and Votan's Fisherman use LibAsync, I have proven to myself that disabling MM stops the error.

    If TSC is a trade addon and uses the lib I would suspect that would be where it's coming from, sales data is collected in the background if not forced. I can play for several hours before my game suddenly decides it's time to collect my recent sales data, or I can force it to collect but that is just damn annoying! :)
    When people say to me........
    "You're going to regret that in the morning"
    I sleep until midday cos I'm a problem solver!
  • Baertram
    Baertram
    ✭✭✭✭✭
    That shown error on consoles is happening cuz LibAsync tries to comoute some data which takes too long.
    That's a restriction of console addons and does not mean LibAsync is the cause alone as ALL addons in combination count towards that limit!

    So it maybe hapening because any addons "in combination" are enabled and LibAsync is the one in the end making the bucket full, afaik.
    But I guess it comes from any adodns that use LibAsync on your console installation, like Maybe a Minimap addon or guild trading history addons etc.
    You could check to disable a few addons that do not use LibAsync, to see if that fixes the error (if you got a way to rebuild the same error reliably).
  • FlopsyPrince
    FlopsyPrince
    ✭✭✭✭✭
    ✭✭✭
    Baertram wrote: »
    That shown error on consoles is happening cuz LibAsync tries to comoute some data which takes too long.
    That's a restriction of console addons and does not mean LibAsync is the cause alone as ALL addons in combination count towards that limit!

    So it maybe hapening because any addons "in combination" are enabled and LibAsync is the one in the end making the bucket full, afaik.
    But I guess it comes from any adodns that use LibAsync on your console installation, like Maybe a Minimap addon or guild trading history addons etc.
    You could check to disable a few addons that do not use LibAsync, to see if that fixes the error (if you got a way to rebuild the same error reliably).

    I am sure that is it. I just don't know which addon pushed it over the edge. I have many but I don't want to lose many. :)

    And I still want the lockpicking one, but I realize that may not come.

    Thanks for your ongoing involvement either way!

    I do assume the exact error I noted can just be ignored. Some others will mess up the system, but I can live with a delay in this case.

    I did have a whacked state each time I showed the map in Cyrodiil until I loaded a different game then came back to ESO on the PS5 and it was back to working as normal.
    PC
    PS4/PS5
  • FlopsyPrince
    FlopsyPrince
    ✭✭✭✭✭
    ✭✭✭
    freespirit wrote: »
    Oh my pop up is random too, not related to vendors at all.

    I have only managed to pin it down to when data is being processed in the background, often I see some read out in chat but not always and the error doesn't appear consistently.

    I've checked the addons I'm currently using and only MM and Votan's Fisherman use LibAsync, I have proven to myself that disabling MM stops the error.

    If TSC is a trade addon and uses the lib I would suspect that would be where it's coming from, sales data is collected in the background if not forced. I can play for several hours before my game suddenly decides it's time to collect my recent sales data, or I can force it to collect but that is just damn annoying! :)

    I thought it might be the TSC data on EU since I have the US one loaded, but I get this same error at time on US. I am not going to worry about it, but I wondered if others on the PS4/5 saw it.
    PC
    PS4/PS5
  • votan73
    votan73
    ✭✭✭
    Either one single job of LibAsync takes longer than 1s. (This is not the way jobs should be designed)
    or
    It could be a false alert on LibAsync as well.
    LibAsync tries to register last, so that everything not using LibAsync is done before.
    If the addon before (like MM) took 999ms, LibAsync will hit the limit, before it can delay execution of jobs.
Sign In or Register to comment.