[Bug] [Solved] Crash after bumping rate limit 1.1.1.0

Discussion in 'AnyStream' started by BuddyFunJet, Apr 14, 2021.

  1. BuddyFunJet

    BuddyFunJet Well-Known Member

    Previously reported problem still in the new version.

    After bumping rate limit, AS 1.1.1.0 crashes out after error messages are cleared.

    Dump reports attached for Amazon and Netflix.
     

    Attached Files:

  2. RedFox 1

    RedFox 1 Super Moderator

    Thanks for the log files, I am sure the developers will look into the issue.
     
  3. 0x0x0x0x0

    0x0x0x0x0 Well-Known Member

    Similar just happened here, but the program died without a coredump at all...
     
  4. Prospere

    Prospere RedFox Development Team

    Thanks for your reports. The issue will be taken care of.
     
    whatever_gong82 likes this.
  5. Bryan Haddock

    Bryan Haddock Member

    I'm running at 1x speed as have been previously. No changes at all except for the new "upgrade".

    Has 1.1.1.0 undergone testing? With default settings the previous version never had issue, and now after allowing the update, this version instantly and continually freezes/locks-up trying to change tabs and interact with the interface. This is noticeable within the first 30 seconds of using the application and attempting multiple tabs. Please FIX. Tx
     
    Lowpro likes this.
  6. Prospere

    Prospere RedFox Development Team

    We need logs. Also, if I understand it correctly, you are experiencing problems with things that have not been modified for quite a few versions. So, yes, we need logs in order to be able to help.
     
    Last edited: Apr 15, 2021
    whatever_gong82 likes this.
  7. Bryan Haddock

    Bryan Haddock Member

    What I described did not indicate a crash or log output. Consistently the app will simply freeze requiring task manager to kill. I'm not aware of any log output under that scenerio...?

    That said, now after sitting idle for hours and coming back to the app it did give producer a "proper crash" and result in the attached. Again, these problems are CONSISTANT and IMMEDIATE when trying to use the interface. Hard to imagine they are difficult to reproduce...
     

    Attached Files:

  8. Pete

    Pete Forum Admin Staff Member

    Simply open task manager, right-click on AnyStream and create a dump file in that situation.
    That would help tremendously.

    Well, that would be great, were it really so, but I've been trying, clicking and interacting and can't reproduce it.
    So maybe your interactions are in some way special?
    Can you describe as precisely as possible, what you do to cause such a freeze?
     
  9. Bryan Haddock

    Bryan Haddock Member

    Sure - while using the product, I saw the notification regarding an upgrade. Proceeded through the upgrade. Reopened the app. The app appeared function on Disney+, initiated a download (still all seemed normal). Once that download was engaged, I clicked the Amazon Prime tab; however, the app froze for 20-40 secs, eventually bringing me to the Amazon page. But once loaded, the interface still started freezing during navigation/search attempts to bring up the desired movie. Eventually between freezes and successes the top boarder of the app indicated "Not Responding". I opened Task Manager and it took multiple "end" operations to actually close the app. I did notice that when Task Manager did remove AnyStream from the Apps list, it populated into the Background Processes list where I performed more End Tasks on it there to completely close the app. After rebooting and reloading the app, I was still seeing freezes and kinda learned it's better to click on all tabs to let them load first before instigating a download on any one of them. Seems loading a tab while another is download exacerbates the issue. Today, I am having better luck - could this be a service issue? I can vouch that my internet connection would not be a factor as other devices and web connections are completed normal during these issues.
     
  10. BuddyFunJet

    BuddyFunJet Well-Known Member

    This bug was fixed in 1.1.1.1. Thanks.
     
    whatever_gong82 and RedFox 1 like this.