Java uses double ram. - sh.itjust.works
sh.itjust.works
Let’s be honest: I only use Java for Minecraft. So I only debugged with it. But all version, server or client, all launchers. All of them use double (or more) RAM. In the game the correctly allocated amount is used, but on my system double or more is allocated. Thus my other apps don’t get enough memory, causing crashes, while the game is suffering as well. I’m not wise enough to know what logs or versions or whatever I should post here as a cry for help, but I’ll update this with anything that’ll help, just tell me. I have no idea how to approach the problem. One idea I have is to run a non-Minecraft java application, but who has( or knows about) one of those? @jrgd@lemm.ee’s request: > launch arguments [-Xms512m, -Xmx1096m, -Duser.language=en] (it’s this little, so that the difference shows clearly. I have a modpack that I give 8gb to and uses way more as well. iirc around 12) > game version 1.18.2 > total system memory 32gb > memory used by the game [https://i.imgur.com/loRZxqu.png] I’m using KDE’s default system monitor, but here’s Btop as well: [https://i.imgur.com/JP3I9MX.png] > this test was on max render distance, with 1gb of ram, it crashed ofc, but it crashed at almost 4gbs, what the hell! That’s 4 times as much I’m on arch (btw) (sry)

No idéa why. Opening this post makes boost crash

  • Annoyed_🦀 @monyet.ccEnglish
    7·
    3 months ago

    Wow, not sure what i expected but yeah it does in fact crash boost.

    Edit: found the reason

    /j

  • Max-P@lemmy.max-p.meEnglish
    4·
    3 months ago

    Logcat for it

    FATAL EXCEPTION: main
Process: com.rubenmayayo.lemmy, PID: 29912
java.lang.RuntimeException: Canvas: trying to draw too large(170161920bytes) bitmap.
	at android.graphics.RecordingCanvas.throwIfCannotDraw(RecordingCanvas.java:266)
	at android.graphics.BaseRecordingCanvas.drawBitmap(BaseRecordingCanvas.java:94)
	at android.graphics.drawable.BitmapDrawable.draw(BitmapDrawable.java:549)
	at ah.a.draw(AsyncDrawable.java:9)
	at ah.e.draw(AsyncDrawableSpan.java:76)
	at android.text.TextLine.handleReplacement(TextLine.java:1507)
	at android.text.TextLine.handleRun(TextLine.java:1676)
	at android.text.TextLine.drawRun(TextLine.java:846)
	at android.text.TextLine.draw(TextLine.java:446)
	at android.text.Layout.drawText(Layout.java:911)
	at android.widget.Editor.drawHardwareAcceleratedInner(Editor.java:2296)
	at android.widget.Editor.drawHardwareAccelerated(Editor.java:2209)
	at android.widget.Editor.onDraw(Editor.java:2140)
	at android.widget.TextView.onDraw(TextView.java:9350)
	at android.view.View.draw(View.java:24627)
	at android.view.View.updateDisplayListIfDirty(View.java:23493)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.draw(View.java:24630)
	at android.view.View.updateDisplayListIfDirty(View.java:23493)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.draw(View.java:24630)
	at android.view.View.updateDisplayListIfDirty(View.java:23493)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at androidx.recyclerview.widget.RecyclerView.drawChild(RecyclerView.java:1)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.draw(View.java:24630)
	at androidx.recyclerview.widget.RecyclerView.draw(RecyclerView.java:1)
	at android.view.View.updateDisplayListIfDirty(View.java:23493)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.draw(View.java:24630)
	at android.view.View.updateDisplayListIfDirty(View.java:23493)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at androidx.coordinatorlayout.widget.CoordinatorLayout.drawChild(CoordinatorLayout.java:137)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.updateDisplayListIfDirty(View.java:23484)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.updateDisplayListIfDirty(View.java:23484)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at androidx.coordinatorlayout.widget.CoordinatorLayout.drawChild(CoordinatorLayout.java:137)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.updateDisplayListIfDirty(View.java:23484)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.draw(View.java:24630)
	at android.view.View.updateDisplayListIfDirty(View.java:23493)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.updateDisplayListIfDirty(View.java:23484)
	at android.view.View.draw(View.java:24357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4576)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4337)
	at android.view.View.updateDisplayListIfDirty(View.java:23484)
	at android.view.View.draw(View.java:24357)
    • Max-P@lemmy.max-p.meEnglish
      3·
      3 months ago

      No, it’s got to be the images. I used Boost to comment on that thread before OP updated with the images, and when I get to the post via my inbox it loads fine. Until I scroll up and the images load, then it crashes.

      • Bangs42@lemmy.worldEnglish
        2·
        3 months ago

        Could it still be the same though? What if there’s an image post that has the same issue in the image? When Boost tries to load that post, wouldn’t it crash too?

        • Max-P@lemmy.max-p.meEnglish
          2·
          3 months ago

          Might depend on the view. I use the list view so I see thumbnails but if you use the card view yeah I could see that crashing it as well. It appears to attempt to display images at whatever resolution it came in.