Browsers also close a comment at `--!>`, `<!-->` and `<!--->`. The scanner looked only for `-->`, so it missed scripts and preloads after such a comment. It now resumes at the first ending a browser recognises, and still hides what is inside ordinary and unfinished comments.
The source map annotation reader split lines on LF only, so a sourceMappingURL comment after a lone CR, U+2028 or U+2029 was missed. It now scans backward over every JavaScript line terminator, counting CRLF once and keeping the 64-line window.
An escaped triple quote inside a GraphQL block string was taken as the end of the string, so braces and comment marks after it were read as document syntax and the operation and later definitions were lost. The escaped delimiter is now consumed as part of the string.
SQLite accepts a quoted column type such as `id "INTEGER" PRIMARY KEY`, which makes the column an alias for the rowid. The reader kept the quotes, so it showed the stored NULL in place of the id. A quoted type is now read with the identifier reader, in all four quoting forms.
A Windows game's folder copied to Linux or macOS has no file with an executable bit, so no program was found and Deep mode skipped the decompiler. A Windows .exe now counts as the program to study on every system, while runtime study starts only a program this computer can run, in both its window and console runs.
A pin estimate that finished after the person cancelled or opened another project's dialog wrote its size into the open draft; an estimate error could also fall through to a toast. The estimate result and every project_pin_create error now name the project (estimate errors also say estimate), and the dialog fills only when the Pin dialog is open for the same normalized project. Estimate errors the open dialog rejects are swallowed; a failed pin creation still tells the person.
Regressions: a late estimate and a late estimate error for another project, an estimate after the dialog closed, and a failed creation that still toasts. Engine tests check the estimate result and both error details, including an open-project failure.
A pin size estimate that finishes after the person cancels or opens another project's dialog is applied to the open dialog. Record the pending change before fixing it.
build_file_read used std::fs::read, so a builder could point it at a multi-GB generated file under app/ or target/ and allocate the whole file before the 256 KiB page was produced; MAX_READ only capped the returned page.
It now reads through platform::fs::read_file_capped with a 16 MiB cap. A file over the cap returns OverLimit with a plain message and a remediation; files at or under the cap page as before. The helper also rejects non-regular files before reading.
Regression: a 16 MiB + 1 text file is refused and a file exactly at 16 MiB still returns its first page; the over-cap assertion failed before the fix, where the tool read it and returned a page. A follow-up roadmap line records build_file_edit, which still reads the whole file.
build_file_read reads the whole file before paging, so a large generated file can freeze or kill the app. Record the pending change before fixing it; the parallel build_file_edit read stays as a follow-up.
A build folder shared by several projects holds every project's programs, and a same-named one there was taken for this project's: Play started it and a new pin copied it. A program outside the project now counts only when Cargo's dep-info file beside it lists sources inside the project, and the newest of the project's own builds is started. A pin made before programs were recorded looks only inside its own copy.
A session that opened one project and then another kept the first project's evidence and open questions in its ledger, so the second project's report and evidence tools mixed both. Opening a different project now clears the ledger, its order, the open questions and the unloaded count before loading the new project's store; reopening the same project still refreshes it in place. Records are saved to their project as they are made, so nothing is lost by clearing.
A path set in Settings → Engines counted as found whenever it existed, so a JDK's folder set for the Java runtime was listed as installed and then run as a program ("permission denied"). A folder is now looked in the way an install folder is, newest version first with digit runs compared as numbers; a folder without the program isn't found, and the message names the folder.
A session that opened project A and then B kept A's ledger and open questions: open_project loaded B's records into the same ledger. The desktop app has one engine for its lifetime, and each rebuild opens its project's investigation, so B's report and evidence tools mixed both projects.
Opening a different project now clears the session ledger, its order, open questions and unloaded count before loading the new project's store. Reopening the same project still refreshes it in place, and a failed unknowns read leaves the current project untouched. unloaded_evidence is recomputed on every open.
Regression: two projects with stored evidence and an open question; switching shows only the new project's records, reopening the same project keeps its ledger, and reopening the first restores its records. A follow-up roadmap line records the open targets and annotations that still survive a switch.
A session that opens a second project currently keeps the first project's evidence and open questions in the ledger. Record the pending change before fixing it.
Follow-up to #1949. A script that runs the headless launcher is kept as the launcher even when it sits in Ghidra's own folder, so what it sets up (its Java, say) isn't dropped. A path a start script names is also followed through its links, so a script that runs a linked ghidraRun leads to the Ghidra folder.
Recovering `with ({undefined: 42}) { result = void 0; }` rewrote `void 0` to `undefined`, which the `with` object can supply, changing the result. Files containing a `with` statement keep their `void` expressions; other rewrites stay on.
The lexer fallback reported `const hook = trpc.users.list.useQuery` as a client call although it only reads a property. An opening call parenthesis (or an optional call) is now required.
The lexer fallback read `require("./\141pp.js")` as a different module path and mis-decoded zero-padded braced Unicode escapes. Legacy octal escapes, every escaped line terminator and braced escapes of any length are now decoded, with checked arithmetic.
A comment between an operation keyword and its name hid the name, and a parenthesis inside a header comment could hide the whole operation. Comments and ignored separators are now skipped before header tokens are read.
A script whose type only resembled a JavaScript type (`application/javascript123`, or one with parameters such as `module; charset=utf-8`) was reported as executable. Types are now matched against the complete supported names, keeping `text/javascript1.0` to `1.5`, as browsers do.
Ghidra's guided setup unpacks Java into the engine store's `jdk` folder, but the Java runtime engine was looked for under `java`, so after that setup the listing still said Java wasn't installed and tools that run a jar (Vineflower, Apktool's check) refused. A guided install now names its store folder in the engine table, and the lookup and installs use it; a test keeps two engines from sharing a store folder.