I rarely ever have Coda crash, but these past two days, it has been crashing for me across different workspaces, different docs, and different tables. A new crash happens about every 30 minutes.
The times when it crashes in the formula editor, it’s always when there is an error, and I’m trying to fix it. If I click on a section that contains an error, it will crash the document. These past two days have been rough because I end up needing to either delete the entire formula to continue, or delete the entire column.
Just now I encountered a column that lost it’s reference for a calculation. But now I can’t even open the formula editor without it crashing, so it forces me to delete the entire column.
Just wondering if anyone else is dealing with this.
I only posted this 21 minutes ago, but it’s getting even worse… and like I mentioned, it’s happening across all my different workspaces and docs. It’s hard to build anything.
レコーディング 2023 07 19 172102 - YouTube
you are not alone. One of my doc crashed as well several times but i couldn’t notice a pattern yet because im working just on this doc at the moment and not on any other ones… I hope this gets fixed until it really starts annoying me…
Same here. Way more crashes.
Oh yeah I got a crash too, it was in the middle of writing a formula. I could refresh the doc without a problem but then it crashed again when I opened the formula editor. I had to Ctrl+z to remove the bad formula
I have one table that over time now has nearly 3700 rows of data.
I’m constantly getting “oops something went wrong…” or memory messages requiring me to refresh the page.
It’s not always that page, it could be others (it happens so much now I just slam the refresh button wo\thinking), I need to document more of the occurrences, but yeah, it is very much annoying.
My system has 64-Gigs of RAM, Chrome is janky w/all the processes it has at times, and Edge isn’t much better but, yes, this started recently - NEVER had this problems using Coda until this month or so.
@Micah_Lucero @Scott_Collier-Weir @Rickard_Abraham @William_Bell
Have you guys already reported that behavior to the Coda-Team or sent them this topic?
Otherwise I would take on this task and open a support ticket tomorrow.
Not yet, just wanted to make sure I wasn’t a one-off case.
It would probably be worth it if we all opened a support ticket though!
Okay, let’s do it then.
I will send them the link to this topic.
Hey y’all! Thanks Jannis for submitting a ticket on this front. I raised this issue with our engineers on your behalf and here’s what I found out.
Sounds like we unintentionally introduced a very serious bug that caused the formula editor to crash, but we believe that it’s now fixed.
If you all wouldn’t mind testing things out and letting us know if things seem better, that would be great!
thanks for the quick reply and solving this issue!
I will let you know if I have any further problems with this issue.
It has definitely improved a lot, thank you guys so much!
I am still experiencing an odd crash that I don’t believe is related to formulas or the formula editor. I have a fairly large doc that holds about 10,000 rows among all of its tables, then an archive table that stores about 3.3 million rows within it’s canvas column (as plain text).
Loading the doc is almost instant-- from refresh to being able to fully intract with the doc and all of its data only takes about 7 seconds, however if I sit within the doc for about and hour or two, the page will completely crash (not just a ‘coda’ crash, but the entire webpage crashes) with the error being ‘out of memory’, even though I’m not even using half of my computers’ ram. Not sure if this a MS Edge issue, or a Coda bug.
It’s not anything urgent, but I haven’t been having this issue before, so just thought I’d bring it up!
Thank you guys again for the quick fix!
I’m glad to hear an issue w/the formula editor was discovered and resolved.
However similar to Micah, I would just have a page open, working in a different browser (non-Coda) window, and when glancing back at the Coda page, I’d notice the page being blank w/an error message in the middle.
I don’t believe that happened at all yesterday however.