[CPU] ResizeBilinearGrad swaps height and width for rectangular inputs in TensorFlow.js 4.22.0

Aperta Adatta ai principianti
#8,757 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@nileshau-afk ci sta già lavorando.

Dal 9/11/2026.

  • #8758 di @ChengCK18 — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
77/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, node.js, typescript

Direzione di ricerca

Leggi tfjs-backend-cpu/src/kernels/ResizeBilinearGrad.ts e controlla la forma dell’output restituita dal kernel del gradiente CPU. Inizia dalla riproduzione minima fornita in scripts/diagnostics/tfjs-resize-minimal.mjs; aggiungi test di regressione per input rettangolari di rango 3 e 4, entrambe le impostazioni di align-corners e quantità variabili di batch e canali. Il lavoro è completato quando l’autodiff CPU restituisce la forma dell’input e i casi di regressione passano.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

comp:backend-cpu type:bug

CPU ResizeBilinearGrad swaps height and width for rectangular inputs (TensorFlow.js 4.22.0)

Prepared 2026-11-08. This report contains synthetic tensors only; no application
models, photograph data, account information or credentials are required.

Environment

  • @tensorflow/tfjs: 4.22.0, including CPU/WebGL backends 4.22.0.
  • Windows x64; Node.js v24.21.0.
  • Independently reproduced in headless Microsoft Edge 157.0.0.0 on Windows.
  • WebGL comparison renderer: Intel HD Graphics 620 through ANGLE / Direct3D11.
  • Pure JavaScript CPU backend, not @tensorflow/tfjs-node.

Minimal reproduction

In an otherwise empty directory, install @tensorflow/[email protected], save the
following as repro.mjs, then run node repro.mjs:

import * as tf from '@tensorflow/tfjs';
await tf.setBackend('cpu');
await tf.ready();
tf.tidy(() => {
  const x = tf.ones([1, 2, 3, 1]);
  console.log(tf.image.resizeBilinear(x, [4, 5], true).shape);
  const gradient = tf.grad(
    image => tf.image.resizeBilinear(image, [4, 5], true).sum()
  )(x);
  console.log(gradient.shape);
});

Expected: forward shape [1,4,5,1]; gradient shape [1,2,3,1].

Actual: forward succeeds, then autodiff throws:

Error in gradient for op ResizeBilinear. The gradient of input 'images' has
shape '1,3,2,1', which does not match the shape of the input '1,2,3,1'

The same failure occurs for a portrait input [512,384,3] resized to [224,224]:
the internal gradient shape is [1,384,512,3] instead of [1,512,384,3].

Test matrix

The same 16 forward/autodiff cases were tested independently in each environment:
eight input shapes, each with alignCorners=false and alignCorners=true.

Input shapes:

[2,3,1], [3,2,1], [3,3,1], [1,2,3,1], [2,2,3,2],
[512,384,3], [384,512,3], [224,224,3]

Large rectangular inputs were resized to [224,224]; other inputs to [4,5].
Both channels and batch size vary in these checks.

Environment/backend Square gradients pass Rectangular gradients fail Forward failures
Node / CPU 4 12 0
Edge / CPU 4 12 0
Edge / WebGL 4 0 (all 12 pass) 0

All successful gradients had the expected input shape and finite values.
This is not a claim about every browser, graphics driver or other backend.

Numerical check and suspected cause

The installed CPU kernel ends with:

return backend.makeTensorInfo([batch, xWidth, xHeight, depth], 'float32', output);

Its input unpacking and accumulation indexing use NHWC with height before width.
The suspected correction is the output shape:

- [batch, xWidth, xHeight, depth]
+ [batch, xHeight, xWidth, depth]

To distinguish a shape problem from incorrect derivative values, the diagnostic
also directly evaluates the raw ResizeBilinearGrad kernel (without changing or
registering any kernels) and compares its flattened values against central
finite differences of a nonuniform weighted sum of the forward resize.

  • Shapes: [1,2,3,1], [1,3,3,1], [2,2,3,2].
  • Both align-corners settings; all input coordinates checked.
  • Central-difference epsilon: 0.001.
  • Maximum absolute discrepancy, Node CPU and Edge CPU: 0.00002975762.
  • Maximum absolute discrepancy, Edge WebGL: 0.00005230308.

This supports an output-shape metadata error for the tested settings. Simply
reshaping the result at application level cannot repair normal tf.grad,
because its shape check throws before returning that result.

No dependency patch has been applied. Proposed upstream regression tests should
cover rectangular rank-3/rank-4 inputs, multiple batches/channels, both
align-corners settings, and comparison against numerical gradients.

Scope

Forward image resizing works in these cases. The failure concerns CPU autodiff
through bilinear resize with rectangular inputs. No pretrained network or
application-specific code is involved.

The diagnostic files in this workspace are:

  • scripts/diagnostics/tfjs-resize-minimal.mjs: standalone minimal reproduction.
  • scripts/diagnostics/tfjs-resize-gradient.mjs: expanded Node/Edge checks.
  • test-data.local/tfjs-resize-gradient/results.json: recorded detailed results.

The expanded runner requires the existing Playwright/Edge installation. The
minimal reproduction requires only TensorFlow.js.

Upstream reporting

Intended tracker: https://github.com/tensorflow/tfjs/issues

The public source page inspected also contains the same swapped expression:
https://github.com/tensorflow/tfjs/blob/master/tfjs-backend-cpu/src/kernels/ResizeBilinearGrad.ts

The GitHub commits API queried on 2026-11-08 identifies the latest commit touching
that file as 087a02a2848db8ba1950c6894fc76d8be3936f11 (2022-11-29).
An immutable source reference is:
https://github.com/tensorflow/tfjs/blob/087a02a2848db8ba1950c6894fc76d8be3936f11/tfjs-backend-cpu/src/kernels/ResizeBilinearGrad.ts

Public GitHub issue search was queried for repo:tensorflow/tfjs ResizeBilinearGrad
and repo:tensorflow/tfjs resize gradient shape. These returned 7 and 2 results
respectively, including pull requests; none of their returned titles matched
this rectangular CPU gradient shape defect. This is a limited duplicate search,
not proof that no prior report exists. No issue has been submitted by this diagnostic.

Only installed 4.22.0 was runtime-tested. The public source view does not establish
a fresh runtime test of current upstream. Check existing issues before filing;
absence of a matching web-search result does not establish that no duplicate exists.

Lingua principale
TypeScript
Stelle
19.2k
Fork
2k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tensorflow/tfjs

Tutte le issue di tensorflow/tfjs

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.