Skip to content
#

sandbox

Here are 1,270 public repositories matching this topic...

fitzgen
fitzgen commented Dec 11, 2020

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

thomasballinger
thomasballinger commented Aug 1, 2021

Related to metering wasm3/wasm3#127 and being able to run a set number of instructions, I'd like to be able to serialize a paused interpreter's state and deserialize it to a new interpreter instance; very roughly,

const interp = new wasm3.Interpreter(module);
interp.interpretNInstructions(100);
const interpState = interp.serializeState();
const interp2 = wasm3.In
techgeeknz
techgeeknz commented Jul 2, 2020

Version of OpenTTD

Since e04ca904a9455afc63aa87db775fe4463ab899b7

The introduction of the minimap screenshot feature appears to be duplicating functionality that will be used elsewhere for drawing the widgets within the minimap window; specifically, the GetMinimapOwner function is very likely to be replicating functionality used by the owner information overlay of the minimap window.

Terasology
keturn
keturn commented Nov 11, 2021

I discovered that setting the Java option -XX:MaxDirectMemorySize is effective at limiting the game's seemingly limitless hunger for memory outside the Java heap. I don't know what heuristic it uses by default, but my processes were regularly multiple gigabytes larger than Xmx led me to believe they should be. (As measured by looking at the process in Linux and noting its Resident Set Size o

nanos
wjhun
wjhun commented Mar 24, 2021

The virtio_scsi driver enqueues buffers to the eventq but does not actually handle them on completion. The following events could be reported to the driver which require some action to be taken:

  • transport reset: This may occur as a result of hotplug events or a device being reset. Sense codes cannot be relied on when new devices or busses appear, so this event needs to be handled.
  • asynchro
Thrive
judge-server

Improve this page

Add a description, image, and links to the sandbox topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the sandbox topic, visit your repo's landing page and select "manage topics."

Learn more