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 am writing to report a significant issue regarding the Rekajs library's memory consumption, which seems to be unusually high compared to expected benchmarks.
When refreshing a page on Google Chrome that utilizes the Rekajs library, the memory usage reported by the Chrome DevTools exceeds 485MB. This is already quite high, but the situation escalates when loading pages with more elements than the provided examples; memory usage can spike to between 800MB and 1GB. For context, when utilizing a full React setup under similar conditions, the expected memory footprint would be around 120MB.
This discrepancy in memory usage suggests there might be a memory leak or an inefficiency within the Rekajs library's handling of DOM elements or state management, especially under heavy load or when rendering complex UIs.
Thank you for your help
The text was updated successfully, but these errors were encountered:
I am writing to report a significant issue regarding the Rekajs library's memory consumption, which seems to be unusually high compared to expected benchmarks.
When refreshing a page on Google Chrome that utilizes the Rekajs library, the memory usage reported by the Chrome DevTools exceeds 485MB. This is already quite high, but the situation escalates when loading pages with more elements than the provided examples; memory usage can spike to between 800MB and 1GB. For context, when utilizing a full React setup under similar conditions, the expected memory footprint would be around 120MB.
This discrepancy in memory usage suggests there might be a memory leak or an inefficiency within the Rekajs library's handling of DOM elements or state management, especially under heavy load or when rendering complex UIs.
Thank you for your help
The text was updated successfully, but these errors were encountered: