The list of known open and resolved issues in 8.6 are shown below. This list will be changing dynamically as new ones are opened and old ones are quashed. Looking for 9.x issues? - see here.
Use the Comment button to see details and contribute your knowledge or experience about a given issue. Voting on issue prioritization is available to Certified Lasso Developers (CLD's), and members of the Lasso Professional Association and the Lasso Development Partners.
If you know of issues not outlined below or if you have any detail you'd like to add please contact firstname.lastname@example.org, and if in reference to a known issue please state the issue number and title.
Memory bug in versions 8.5.6b1 and 8.5.6 final, where the lasso8 service process is taking 1.15 GB of RAM, as found in the console log.
Lasso uses up all available memory on the server and never releases it.
Generic (cause unknown) site crashing error message.
When Lasso consumes a lot of memory (like a runaway thread) it can't make more sessions.
Loop_continue crashes when given certain scripts.
Under certain circumstances, an unclosed custom container tag can crash Lasso.
When using loop_continue in a certain context, Lasso crashes.
If the Postgres maintenance table name is changed from the default 'postgres', Lasso returns an error.
Fail inside a handle tag should pass the error outside of a surrounding protect block. Only works in some cases.
When creating LassoApps and using the LassoApp_Create tag, sometimes a VM error (too much memory requested) is encountered.
Incorrect mail header enoding for subjects containing UTF-8 text.
Users can experience a namespace resolution issue if a mixed custom tag is created using both _ and -namespace in the definition.
There is a difference in arithmetic precision between normal + and += . Using + gives 6 digits precision, while using += gives "full" precision.
Lasso throws an error or sends an incomplete page when the file length is too long or contains an Appearance object.
The JDBC connector does not escape quotes within SQL statements which could lead to SQL injection. Also, binary data is not automatically handled.
Windows Installers for newer versions of Windows and IIS need to be updated and released.
Inlines -host & double byte characters issues need to be resolved.
SQL Queries do not release fast enough.
Due to a limitation in the used libraries, a Unicode error is observed.
Lasso crashes and fails to automatically restart on Cent OS 5.
This can prevent emails from being sent from Lasso, which might not immediately be noticed.
The SMTP queue fails with an error when a recipient mistakenly contains an extended character.
Depending on where -encoding is used, the pdf tags incorrectly handle foreign language characters by either converting them to white space or omitting them completely.
Uploading and manipulating .TIF images causes Lasso to crash.
When using action_statement, Lasso will sometimes show the correct characters, and other times will show the wrong characters.