This message was deleted.
# report-bugs
s
This message was deleted.
1
j
Which browser are you on?
v
Arc
I got it every time I refresh a graphite page actually 😅 not a huge blocker as it's easy to fix and I don't lose any setup
j
we do try to clear indexeddb ourselves but not all browsers support the api we use to do so properly… haven’t tested arc specifically, I believe @Pranathi Peri has been using it though…
👍 1
p
I haven't used Graphite specifically with Arc too much (I unfortunately have chrome and arc open at all times) but I think there is some shaky compatibility between Graphite/Arc
v
Ok good to know! Thanks a lot!
m
Cc @Greg
v
I'm stopping reviews on Graphite. It became unusable. You never know if your changes were applied or not (I lost a full review with comment already). I have to try to close the window each time to check if my action was "committed" (so I get the "are you sure you want to close this tab" warning) and I have no idea what to do when not the case. I have to clear cache almost every time I'm trying to use it. It's really sad I really enjoy the UI Sorry, will try again in a month or two to check if fixed! As the team we had (and still have) the same issue with Linear that also heavily relies on IndexDb and a fully async architecture so the site is "snappy". I prefer blocking and consistent than snappy and unreliable.
m
Appreciate the tough feedback here - @Tomas Reimers just pushed a fix which should significantly reduce memory usage
🙏 1
v
OK thanks a lot for this! I'll report back if I see improvements
Well, nothing seemed to have changed. Can't submit a review ("nothing happens" when I submit) without "clear site data/refresh" (and then I lost a comment)
p
You're still using arc correct?
v
I don't know if changes were made but it seems waaaaay better lately (yesterday + today was OK) Thank you if you did something, else I'll thank the "random/fixed by magic" gods.
j
It’s possible Arc did something on their end — otherwise no changes here since Tomas fixed memory usage
🙏 1
👍 1