Lasso 8.6 Issues List
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 bugs@lassosoft.com, and if in reference to a known issue please state the issue number and title.
Showing 1 - 25 of 37
- 1
- 2
Memory Issue
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 Memory Hog
Lasso uses up all available memory on the server and never releases it.
Unidentified Broken Pipe
Generic (cause unknown) site crashing error message.
Session Memory
When Lasso consumes a lot of memory (like a runaway thread) it can't make more sessions.
Loop_continue Problem
Loop_continue crashes when given certain scripts.
Unclosed Custom Container
Under certain circumstances, an unclosed custom container tag can crash Lasso.
Loop_continue Crash
When using loop_continue in a certain context, Lasso crashes.
Postgres Maintenance Table Name
If the Postgres maintenance table name is changed from the default 'postgres', Lasso returns an error.
Fail Inside Handle
Fail inside a handle tag should pass the error outside of a surrounding protect block. Only works in some cases.
LassoApp_Create VM Error
When creating LassoApps and using the LassoApp_Create tag, sometimes a VM error (too much memory requested) is encountered.
Mail subject encoding, UTF-8
Incorrect mail header enoding for subjects containing UTF-8 text.
Namespace Resolution Issue
Users can experience a namespace resolution issue if a mixed custom tag is created using both _ and -namespace in the definition.
Decimal Precision Variance
There is a difference in arithmetic precision between normal + and += . Using + gives 6 digits precision, while using += gives "full" precision.
Libxml Error
Lasso throws an error or sends an incomplete page when the file length is too long or contains an Appearance object.
DB2 Quotes and Binary
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
Windows Installers for newer versions of Windows and IIS need to be updated and released.
Inlines -host & Characters
Inlines -host & double byte characters issues need to be resolved.
Queries Release Speed
SQL Queries do not release fast enough.
Unicode Format
Due to a limitation in the used libraries, a Unicode error is observed.
Lasso Restart Fail
Lasso crashes and fails to automatically restart on Cent OS 5.
DNS Deafness
This can prevent emails from being sent from Lasso, which might not immediately be noticed.
SMTP Error With Extended Characters
The SMTP queue fails with an error when a recipient mistakenly contains an extended character.
PDF Tags and Foreign Characters
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.
ImageMagick and .TIFs
Uploading and manipulating .TIF images causes Lasso to crash.
Action_statement Extended Characters
When using action_statement, Lasso will sometimes show the correct characters, and other times will show the wrong characters.
Showing 1 - 25 of 37
- 1
- 2
