[Bug]: Segfault loading fonts

[TotalChaos05]

Software Version

3.0.1

What Happened?

The system segfaults on loading fonts

Access Type: Write
when loading a custom font
Access Type: Read
when loading "standard"

What was Expected?

The fonts should load without segfaulting

Code to Reproduce

fontdata = {file = "resources/fonts/m6x11plus.ttf", render_scale = self.TILESIZE*10, TEXT_HEIGHT_SCALE = 0.83, TEXT_OFFSET = {x=10,y=-20}, FONTSCALE = 0.1, squish = 1, DESCSCALE = 1}
font = love.graphics.newFont( fontdata.file, fontdata.render_scale)

Console

Nintendo 3DS

Firmware Version(s)

11.17.0-50U

Custom Firmware Version

13.2.1

Execution Method

Homebrew Menu

Code of Conduct

• I have read the Code of Conduct and agree to these terms

[TotalChaos05]

Note that i am porting a game, rather than writing from scratch, which could also be the source of the issue

[TurtleP]

If you can dump the exception when it happens and upload it, I can debug it further. My initial suspicion is it’s possible that you’re running out of linear memory, which is not caught properly on versions before 3.1.0.

[TotalChaos05]

ill upload a dump once i get home is 3.1.0 only available if i compile myself?

…

________________________________ From: Serena Postelnek ***@***.***> Sent: Saturday, January 11, 2025 11:56:00 AM To: lovebrew/lovepotion ***@***.***> Cc: Basil Keeler ***@***.***>; Author ***@***.***> Subject: Re: [lovebrew/lovepotion] [Bug]: Segfault loading fonts (Issue #246) If you can dump the exception when it happens and upload it, I can debug it further. My initial suspicion is it’s possible that you’re running out of linear memory, which is not caught properly on versions before 3.1.0. — Reply to this email directly, view it on GitHub<#246 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQZAPLHWX4YZZF7VA2HJP332KFLLBAVCNFSM6AAAAABVAEF3QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVGM2TOMZYGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[TotalChaos05]

crash_dump_00000001.dmp
heres the crash dump

if the issue is memory, is there any way i can make it utilize the full n3ds memory instead of the (assumed) o3ds limit