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
When the view child requests more RAM, text_area does not try to increase its own RAM quota. The effect is that the editor may fail to render on large screens with Large font sizes (e.g. 4k screen with font size set to Large) unless it is given a high default RAM quota to satisfy the view RAM request.
While a large upfront RAM quota mitigates the problem, the better solution would be for text_area to react to child RAM requests by attempting to raise its own quota if necessary.
The text was updated successfully, but these errors were encountered:
atopia
added a commit
to atopia/genode
that referenced
this issue
Nov 15, 2024
When trying to open a file in the Files view with font size set to
Large on 4k screens, the editor's / `text_area`'s `view` child fails to
bump its RAM quota when the editor's default quota is too small.
To mitigate the issue, bump the editor's default quota to 80MiB.
The long-term fix would be for the editor to request more RAM from the
runtime to satisfy the `view` RAM request.
Issue genodelabs#5356
Issue genodelabs#5383
When trying to open a file in the Files view with font size set to
Large on 4k screens, the editor's / `text_area`'s `view` child fails to
bump its RAM quota when the editor's default quota is too small.
To mitigate the issue, bump the editor's default quota to 80MiB.
The long-term fix would be for the editor to request more RAM from the
runtime to satisfy the `view` RAM request.
Issue #5356
Issue #5383
When trying to open a file in the Files view with font size set to
Large on 4k screens, the editor's / `text_area`'s `view` child fails to
bump its RAM quota when the editor's default quota is too small.
To mitigate the issue, bump the editor's default quota to 80MiB.
The long-term fix would be for the editor to request more RAM from the
runtime to satisfy the `view` RAM request.
Issue #5356
Issue #5383
When the
view
child requests more RAM,text_area
does not try to increase its own RAM quota. The effect is that the editor may fail to render on large screens with Large font sizes (e.g. 4k screen with font size set to Large) unless it is given a high default RAM quota to satisfy theview
RAM request.While a large upfront RAM quota mitigates the problem, the better solution would be for
text_area
to react to child RAM requests by attempting to raise its own quota if necessary.The text was updated successfully, but these errors were encountered: