Returning array broken with mode:dev #719

Activity

1. fuzzie360 commented on Jul 22, 2026

   

   fuzzie360

   on Jul 22, 2026

   Member

   More actions

   As part of reviving the project, we're closing stale support questions and version-specific reports from older releases. A lot changed today: 2.17.0–2.19.2 shipped and are on npm (npm install gpu.js), installs work on modern Node, new GPU() works in current browsers, Apple Silicon precision issues are fixed, and CI now guards every change. If this is still relevant on gpu.js@2.19.2, please open a fresh issue with a repro — happy to help. (See #807 for the full status update.)
2. fuzzie360

   closed this as not plannedon Jul 22, 2026
3. rotu commented on Jul 23, 2026

   

   rotu

   on Jul 23, 2026

   Author

   More actions

   @fuzzie360 This still fails in exactly the same way. Could you please reopen?
4. fuzzie360 commented on Jul 24, 2026

   

   fuzzie360

   on Jul 24, 2026

   Member

   More actions

   Reopened — thanks for re-verifying on 2.19.2. Apologies for sweeping this up in the stale batch-close; it's back in the triaged bug queue.
5. fuzzie360

   reopened this on Jul 24, 2026
6. fuzzie360

   closed this as completedin 5df02deon Jul 24, 2026
7. fuzzie360 commented on Jul 24, 2026

   

   fuzzie360

   on Jul 24, 2026

   Member

   More actions

   Fixed upstream in gpu-mock.js v1.4.0 — mode: 'dev' delegates kernels entirely to gpu-mock.js, whose mock loops assigned each thread's return value into a Float32Array slot, so array returns coerced to NaN. Array-returning kernels now yield a Float32Array per thread, matching the real backends. Verified against your exact repro through gpu.js dev mode: [[1,2,3],[1,2,3],[1,2,3],[1,2,3]].

   One step remains before this closes: publishing gpu-mock.js@1.4.0 to npm (maintainer access being sorted, same story as gpu.js's was) and bumping the dependency here. Will update when it ships.

   👍React with 👍1Reacted by Dan Rose
8. fuzzie360

   added a commit that references this issue on Jul 26, 2026

   fix: Array-returning kernels in dev mode

   ...

   This issue will close once commit 0da8078 is merged into the 'develop' branch.

   0da8078
9. fuzzie360 commented on Jul 26, 2026

   

   fuzzie360

   on Jul 26, 2026

   Member

   More actions

   Shipped in 2.19.4, now on npm — npm install gpu.js@2.19.4.

   The fix went upstream into gpu-mock.js 1.4.0 (which mode: 'dev' delegates to) and gpu.js now depends on that release rather than the fork it had been pinned to. Verified from a clean npm install of 2.19.4:

   const { GPU } = require('gpu.js');
   const gpu = new GPU({ mode: 'dev' });
   const kernel = gpu.createKernel(function() { return [1, 2, 3]; }, { output: [4] });
   kernel(); // [[1,2,3], [1,2,3], [1,2,3], [1,2,3]]  — was NaN throughout

   Array returns now match the real backends in one, two and three dimensions, and number returns still come back as a flat Float32Array. test/features/dev-mode.js covers all of that plus explicit parity against cpu mode, so running return-arrays.js under dev — your original suggestion — would pass too.

   Thanks for re-verifying this after the batch-close; both issues you asked to reopen turned out to be real, and this one reached further than gpu.js itself.