1. Anders Ruud
  2. love
  3. Issues

Issues

Issue #606 duplicate

Windows 7: love.graphics.print crashes when a space is printed

radlstadl
created an issue

See also https://github.com/Germanunkol/trAInsported/issues/20.

On Windows 7 (64 bit), valid for both 32 and 64 bit variant, the system crashes when calling love.graphics.print() with a string that contains a space character. I am new to Löve but this program works (just one file mail.lua):

function love.draw() love.graphics.print("Hello-Love", 30, 100) end

But printing any space leads to the crash in the graphics DLL:

function love.draw() love.graphics.print("Hello Love", 30, 100) end

Problem signature: Problem Event Name: APPCRASH Application Name: love.exe Application Version: 0.8.0.0 Application Timestamp: 4f78fc8a Fault Module Name: atio6axx.dll Fault Module Version: 6.14.10.9606 Fault Module Timestamp: 4b7374ac Exception Code: c0000094 Exception Offset: 0000000000815c16 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1031 Additional Information 1: 38bf Additional Information 2: 38bf30f4d8c1fbc961fc2c5bcfdb7e19 Additional Information 3: d6fb Additional Information 4: d6fbac5e1b9396aadb42fbd99c3eaf3d

Does anyone know how I could help to solve this issue? I am new to Löve and learned about it only due to trAInsported. And I am new to trAInsported and learned about it only due to a news at heise.de.

I set the priority to "blocker", for at least on several Windows 7 installations even the smallest sample applications do not work anymore. The same binaries work on a Windows XP installation. However, I do not know if all Windows-7-installations are broken, or only mine. Or if I just downloaded the wrongt love interpreter...

I have downloaded love-0.8.0-win-x86.zip and love-0.8.0-win-x64.zip with these SHA1 check sums: 689987484fc858cea8b64cfa5956f414aa89ca69 love-0.8.0-win-x64.zip c1f670160e4cfcc7bc24d76c53a243e8a68c0dc2 love-0.8.0-win-x86.zip

Best regards, radlstadl.

Comments (4)

  1. radlstadl reporter

    Thank you, Boolsheet. This build works also on my machine. Seems that you can set this issue to a duplicate to #406 (or just close it). Best regards, malzahn.

  2. Log in to comment