Squish 9.1.1 Known Issues

Last edited on

Known Issues - Squish 9.1.1 Release

(Known Issues of previous version)

Release Date: November 11th, 2025

Recommended Update: n/a

Squish for Java

No Java 25 support yet

It is currently not possible to automate tests of Java AUTs built with Java 25 (released in September 2025) using Squish. When Squish starts a Java 25 AUT - either from the Squish IDE or from the command-line (e.g. in continuous integration environment) - the following error message appears in the squishrunner log: Exception in thread "main" java.lang.VerifyError: StackMapTable error: bad offset. This is due to changes introduced in Java 25 into how JVM loads and verifies application code. These changes conflict with the technique Squish is using to instrument Java AUTs to enable test automation.

There is currently no workaround. If possible, build and run your Java AUTs with Java 24 or earlier, until functional support for Java 25 is added in a future Squish release (SQUISH-20163).

Squish for Web

Time-out or crash starting the Google Chrome browser from Squish in certain Qt-based Linux desktop environments

When automating tests of websites in the Google Chrome browser, starting the browser from Squish may time out and eventually fail in certain Qt-based Linux desktop environments (for example: KDE or LXDE). As a result, recording and replaying tests, as well as launching the browser in spy mode (the Launch AUT functionality in the Squish IDE) is not possible without a workaround (see below).

This issue is caused by mismatch between system Qt libraries loaded by the recently introduced Chrome Qt backend, designed to improve Chrome's integration into Qt-based desktops, and the Qt libraries shipped with and used by Squish for Web. This may result in undefined behaviour, typically manifesting as connection timeout or browser crash.

Workaround