You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed marimo already (0.9.27) chooses not to send the full dataframe and do the histograms if > 20k rows or > 40 columns so I tried hitting the worst case of 20k rows and 40 columns. This gives about 15MB of csv on the wire, which seems pretty reasonable, but rendering the histograms is very sluggish and has been occasionally enough to give me the "Not enough memory to open this page" chrome error. It seems to be OK the first time I render one such dataframe in a tab, but sometimes crashes later. I haven't been able to pin down exactly when it does. One possible trigger is switching tabs (in Chrome) away and back again. I speculate that the problematic notebooks that I and colleagues have seen at work are ones with this kind of size dataframe, perhaps with multiple such rendered in one notebook. Sorry this is a bit vague and I can't yet give you a deterministic repro.
The text was updated successfully, but these errors were encountered:
Originally posted by @alexscordellis in #2991 (comment)
I noticed marimo already (0.9.27) chooses not to send the full dataframe and do the histograms if > 20k rows or > 40 columns so I tried hitting the worst case of 20k rows and 40 columns. This gives about 15MB of csv on the wire, which seems pretty reasonable, but rendering the histograms is very sluggish and has been occasionally enough to give me the "Not enough memory to open this page" chrome error. It seems to be OK the first time I render one such dataframe in a tab, but sometimes crashes later. I haven't been able to pin down exactly when it does. One possible trigger is switching tabs (in Chrome) away and back again. I speculate that the problematic notebooks that I and colleagues have seen at work are ones with this kind of size dataframe, perhaps with multiple such rendered in one notebook. Sorry this is a bit vague and I can't yet give you a deterministic repro.
The text was updated successfully, but these errors were encountered: