Atomics.isLockFree()

La méthode statique Atomics.isLockFree() est utilisée afin de déterminer si on doit utiliser des verrous (locks) ou des opérations atomiques. Elle renvoie true si la taille donnée correspond à une des propriétés BYTES_PER_ELEMENT d'un des types TypedArray.

Syntaxe

Atomics.isLockFree(taille)

Paramètres

taille: La taille en octets qu'on souhaite vérifier.

Valeur de retour

Un booléen indiquant si l'opération se déroule sans verrou.

Exemples

Atomics.isLockFree(1); // true
Atomics.isLockFree(2); // true
Atomics.isLockFree(3); // false
Atomics.isLockFree(4); // true
Atomics.isLockFree(5); // false
Atomics.isLockFree(6); // false
Atomics.isLockFree(7); // false
Atomics.isLockFree(8); // true

Spécifications

Spécification	État	Commentaires
ECMAScript (ECMA-262) La définition de 'Atomics.isLockFree' dans cette spécification.	Standard évolutif	Définition initiale avec ES2017.

Compatibilité des navigateurs

Update compatibility data on GitHub

	Ordinateur						Mobile						Serveur
	Chrome	Edge	Firefox	Internet Explorer	Opera	Safari	Webview Android	Chrome pour Android	Firefox pour Android	Opera pour Android	Safari sur iOS	Samsung Internet	Node.js
`isLockFree`	Chrome Support complet 68 Support complet 68 Aucun support 60 — 63 Notes Notes Chrome disabled `SharedArrayBuffer` on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This was a temporary removal while mitigations were put in place.	Edge Support complet 79 Support complet 79 Aucun support 16 — 17 Notes Notes Support was removed to mitigate speculative execution side-channel attacks (Windows blog).	Firefox Support complet 78 Support complet 78 Support complet 57 Notes Désactivée Notes Support was disabled by default to mitigate speculative execution side-channel attacks (Mozilla Security Blog). Désactivée From version 57: this feature is behind the `javascript.options.shared_memory` preference (needs to be set to `true`). To change preferences in Firefox, visit about:config. Aucun support 55 — 57 Aucun support 46 — 55 Désactivée Désactivée From version 46 until version 55 (exclusive): this feature is behind the `javascript.options.shared_memory` preference (needs to be set to `true`). To change preferences in Firefox, visit about:config.	IE Aucun support Non	Opera Aucun support Non	Safari Aucun support 10.1 — 11.1	WebView Android Aucun support 60 — 63 Notes Aucun support 60 — 63 Notes Notes Chrome disabled `SharedArrayBuffer` on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place.	Chrome Android Aucun support 60 — 63 Notes Aucun support 60 — 63 Notes Notes Chrome disabled `SharedArrayBuffer` on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place.	Firefox Android Support complet 57 Notes Désactivée Support complet 57 Notes Désactivée Notes Support was disabled by default to mitigate speculative execution side-channel attacks (Mozilla Security Blog). Désactivée From version 57: this feature is behind the `javascript.options.shared_memory` preference (needs to be set to `true`). To change preferences in Firefox, visit about:config. Aucun support 55 — 57 Aucun support 46 — 55 Désactivée Désactivée From version 46 until version 55 (exclusive): this feature is behind the `javascript.options.shared_memory` preference (needs to be set to `true`). To change preferences in Firefox, visit about:config.	Opera Android Aucun support Non	Safari iOS Aucun support 10.3 — 11.3	Samsung Internet Android Aucun support Non Notes Aucun support Non Notes Notes Chrome disabled `SharedArrayBuffer` on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place.	nodejs Support complet 8.10.0

Légende

Support complet: Support complet
Aucun support: Aucun support
Voir les notes d'implémentation.: Voir les notes d'implémentation.
Une action explicite de l'utilisateur est nécessaire pour activer cette fonctionnalité.: Une action explicite de l'utilisateur est nécessaire pour activer cette fonctionnalité.

Voir aussi

Atomics