Looking Glass sometimes provides incorrect interface information
Description of the bug (be specific): When some users use looking glass, after awhile (or a couple minutes) the clients will begin providing invalid information to the script about interfaces (there may be some other issues too but this is the main thing). Specifically things such as saying the bank isn't open when it is, saying the bank is empty when it isn't, being unable to find an item in the inventory, saying something in the make all interface is there when it really isn't, trying to withdraw an item in a location that is empty, and many more similar issues. Also experience a stack overflow sometimes with interfaces.
There is definitely some issues with looking glass and it would be really great if they could be addressed. Feel free to read my nBlast Furnace forum thread and see that > 90% of bug reports are looking glass issues. The script averages 200 days of runtime every 24 hours and the script runs perfect on a regular client (regular client users make up most of the runtime and they hardly, if ever, report bugs). Almost all the bug reports that come in are interface issues with looking glass. https://tribot.org/forums/topic/77771-300k-1mhr-nblast-furnace-low-requirements-fresh-account-preparing-ge-restocking-muling-all-efficiency-items-and-methods-supported/page/43/
How often the bug occurs: Seemingly random, some users experience it consistently while others don't experience it often.
Triggers of the bug (if known): Looking Glass with a script that uses interface data (literally any script that uses Banking)
Java version: Several different java versions have been tried, ex. java version "1.8.0_191"
Max Heap Size: N/A
TRiBot client version: TRiBot Version: TRiBot Release 10.14_1
Looking Glass (yes/no): Yes
Operating System: N/A
Script Name: N/A
TRiBot Old-School or RS3: OSRS
Client Debug: see below for examples
Bot Debug: see below for examples
Screenshots (if any):
Stack overflow w/ interfaces: https://pastebin.com/wY7GuqEV
Unable to find an item in the bank (using both Banking.withdraw and Banking.find) (Note that "return status 2" means Banking.getAll().length == 0) https://imgur.com/CjnhS1I
Trying to withdraw an invisible item (note the stack trace and see that this is using Banking.withdraw, a tribot method). The script (Banking.withdraw) would scroll down to this arbitrary location in the bank even if the user scrolled back up. https://i.imgur.com/1JXhwLB.mp4
For a ton more examples, search through my thread posted above for "lg" and "looking glass" and you'll see that I can easily predict when a user is using LG based on the bug reported (because the bug doesn't happen on the regular client).
Any progress made towards looking glass would be extremely appreciated by me and many users of tribot.
To be clear, this issue happens on both resizable mode + fixed mode.