Problem with memory allocation for background images? Not possible to have more than 1 Background layer open

[anonymous]

What steps will reproduce the problem?

1. I open my usual (small) work area in Open street map carto layer
2. I open Bing background layer
3. I get red error message "not enough memory to draw layer Bing aerial image", the Layer is shown in the layer list, but not drawn onto screen
4. I close the Open streetmap carto layer
5. now Bing layer is shown immediately

6 but then I cannot open Open streetmap carto layer anymore until I close Bing layer

Same works with other layers as Esri, Mapbox, Maxar too...
Seems to be a general problem checking or allocating memory to more than 1 Layer at one time...

What is the expected result?

multiple layers open as usual

What happens instead?

can open only on layer at one time, even if you zoom in very much to reduce downloadable data ammount

Please provide any additional information below. Attach a screenshot if possible.

Just updated to newest OSM and Java versions, the error did not occure yesterday. Restarted PC after update and error.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2022-08-29 16:59:00 +0200 (Mon, 29 Aug 2022)
Build-Date:2022-08-30 01:30:57
Revision:18543
Relative:URL: ^/trunk

Identification: JOSM/1.5 (18543 de) Windows 10 64-Bit
OS Build number: Windows 10 Home 2009 (19043)
Memory Usage: 139 MB / 247 MB (32 MB allocated, but free)
Java version: 1.8.0_341-b10, Oracle Corporation, Java HotSpot(TM) Client VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 1920×1080 (scaling 1.00×1.00) \Display1 1920×1080 (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→32×32, 32×32→32×32
System property file.encoding: Cp1252
System property sun.jnu.encoding: Cp1252
Locale info: de_DE
Numbers with default locale: 1234567890 -> 1234567890

Plugins:
+ turnrestrictions (36011)

[skyper]

You need to allocate more memory on start up. See also my comment on #22330.