Known issues in CraftOS-PC

[MCJack123]

This page lists some known issues in the latest version of CraftOS-PC (v2.6.3). These will be fixed with the next release.

(None so far)

Previous versions

v2.6.2

• websocket.receive currently does not function properly. Please listen to the websocket_message event instead for now, or grab the latest artifact build.
• CraftOS-PC may very rarely crash when canceling a timer that's in the process of firing.
• Running detach or calling periphemu.remove on a debugger causes a crash.

v2.6.1

• Launching a new debugger causes a crash.
  • Workaround: Download the fixed version of Lua, and drop it into the CraftOS-PC installation folder.
• Some functions from the original os API in Lua are retained, including os.getenv. These should not be used, and it is recommended that these functions are removed in a startup file.
• If a computer shuts down while the "Computer not responding" window is open, CraftOS-PC will crash after a button on the window is clicked.

v2.5.5

• Some users have reported lag in programs that poll a large number of events. Investigation into this issue is ongoing and will be fixed by the next release.
• Passing a poorly-formed URL to an HTTP function can cause the computer to crash.
• A Too long without yielding error may be sent after a few seconds if Ctrl+T is held while a program is running.
• Adding any peripheral with a display crashes when in raw mode.
• Using a URL without a path (e.g. https://www.google.com) may cause a website to send a 400 Bad Request response.
  • Workaround: Add a / to the end if no path was specified.
• Canceling a timer that doesn't exist may cause a crash.
• Modems may randomly cause CraftOS-PC to crash.
• Using %2F to encode a slash will decode it back to a slash, breaking any API that requires the distinction.
• Clicking twice at the same point on a monitor will cause the second touch event to not be sent.

v2.5.4

• CraftOS-PC v2.5.2 and early versions of v2.5.3 on Windows do not run the installer after downloading it.
  • Workaround: Either manually download the installer from the releases page, or navigate to C:\Users\<username>\AppData\Local\Temp and run setup.exe.
• Attempting to use term.getSize(mode) in non-graphics mode fails when using multishell (or redirected to a window)
  • Workaround: Use term.native().getSize(mode), or switch to graphics mode first
• HTTP handle reading may occasionally not work, especially in binary mode.
• Using modulo with a negative number and a positive number where |a| % |b| = 0 results in b instead of 0.

v2.5.3

• The User-Agent and Accept-Encoding headers are missing from WebSocket connections unless manually specified.
  • This was also a bug in CC:T until 1.95.3 (Websockets do not supply User-Agent cc-tweaked/CC-Tweaked#730)... so this was accurate I guess?
• Computers may randomly shut down with "Too long without yielding" when running in a tight loop.
• Some interactions with modems may cause a crash.
• WebSockets may linger up to 30 seconds after close is called on them.
• Binary WebSocket messages are not properly supported.
• HTTP request functions do not entirely check URLs passed to them.
• Using file.read(n) on text handles may read data past the end of the file.
• debug.upvalueid and debug.upvaluejoin are missing from the debug API.

v2.5.2

• HTTP handles are not automatically closed after use.
  • Workaround: Always close HTTP handles. (You should do this anyway.)
• Resizing the window to 0x0 causes a deadlock.
• Using the hardware renderer on macOS with monitors with different DPI scales (Retina/non-Retina) occasionally causes the text to render too small.
  • Workaround: Use the software renderer instead.

v2.5.1.1

• Raw mode is currently not working on macOS. The cause of the issue is some sort of invalid mutex lock; however, the reason for this is currently unknown.
• The modulo operator sometimes produces incorrect results due to an inaccurate implementation in base Lua.
  • Workaround: Use math.fmod for the time being.
• Setting the scroll direction to "natural" or "Australian" does not invert scrolling as expected.
• os.epoch("local") does not return local time as expected, instead returning UTC time.
• Some usages of fs.getFreeSpace and fs.getCapacity may cause an infinite loop, crashing the program.

v2.5.1

• Sometimes, random crashes can occur when using coroutines while debugging is enabled, due to a memory corruption bug. It is unknown what the direct cause of this is, but it has to do with resuming coroutines.
  • Workaround: Disable the debug_enable option in the config

v2.5

• CraftOS-PC crashes with "Vector2D index out of range" when using term.drawPixels
  • Workaround: Manually check that all indices passed to term.drawPixels are correct
• CraftOS-PC Online does not properly display on Hi-DPI screens (scaling > 150%).
• Receiving data from WebSockets results in junk data being added at the beginning of the string.
• WebSockets left open when rebooting will not be closed, reducing the number of WebSocket connections available before hitting the limit.
  • Workaround: Close all WebSocket handles before rebooting.
• CraftOS-PC and CraftOS-PC Accelerated are not able to be installed to the same directory.
  • Workaround: Install them in separate directories.

[LoganDark]

Workaround: Manually check that all indices passed to term.drawPixels are correct

Actually, the workaround that was merged was that pixels simply will not be copied if they go off-screen.

[MCJack123]

Well, that's the fix; this is specifying how to work around the bug until the fix is released.