Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-228507] Unusual Script Errors on Some SL Regions, Not on Other Regions #6579

Closed
1 task
sl-service-account opened this issue Apr 16, 2020 · 4 comments
Closed
1 task

Comments

@sl-service-account
Copy link

sl-service-account commented Apr 16, 2020

What just happened?

The LAQ Bento Mesh Head HUD v3.06 began returning a script error today, but only on some regions.

And yes, I am reporting this from a third-party viewer. The viewer does not run the script; the region does. I was made aware of the error in the LAQ Updates group chat, and I followed up.

What were you doing when it happened?

The HUD produces a script error on attach and on detach. The error is repeated several times but does not continue to repeat itself after the attach/detach action.

[20:20] LAQ Bento - [HUD] 3.06: llBase64ToInteger received a invalid base64 string.

What were you expecting to happen instead?

No script error.

Other information

The error only occurs on regions running Second Life Server 2020-04-10T18:39:41.540037.

To be clear, I am unable to repro on Second Life Server 2020-04-03T19:49:49.539684.

Links

Duplicates

Original Jira Fields
Field Value
Issue BUG-228507
Summary Unusual Script Errors on Some SL Regions, Not on Other Regions
Type Bug
Priority Unset
Status Closed
Resolution Accepted
Reporter Paige Theseus (paige.theseus)
Created at 2020-04-16T03:27:59Z
Updated at 2020-05-15T16:27:32Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'Date of First Response': '2020-04-16T03:22:06.922-0500',
  "Is there anything you'd like to add?": 'The error only occurs on regions running Second Life Server 2020-04-10T18:39:41.540037.\r\n\r\nTo be clear, I am unable to repro on Second Life Server 2020-04-03T19:49:49.539684.',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Simulator',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'The LAQ Bento Mesh Head HUD v3.06 began returning a script error today, but only on some regions.\r\n\r\nAnd yes, I am reporting this from a third-party viewer. The viewer does not run the script; the region does. I was made aware of the error in the LAQ Updates group chat, and I followed up.',
  'What were you doing when it happened?': 'The HUD produces a script error on attach and on detach. The error is repeated several times but does not continue to repeat itself after the attach/detach action.\r\n\r\n[20:20] LAQ Bento - [HUD] 3.06: llBase64ToInteger received a invalid base64 string.',
  'What were you expecting to happen instead?': 'No script error.',
  'Where': 'LAQ Main Store, http://maps.secondlife.com/secondlife/LAQ/126/108/76',
}
@sl-service-account
Copy link
Author

Paige Theseus commented at 2020-04-16T03:52:48Z

Repro in SL Viewer: 

 

Second Life Release 6.3.8.538264 (64bit)
Release Notes

You are at 128.2, 90.5, 76.0 in LAQ located at sim10442.agni.lindenlab.com (216.82.51.148:13009)
SLURL: http://maps.secondlife.com/secondlife/LAQ/128/90/76
(global coordinates 270,208.0, 280,410.0, 76.0)
Second Life Server 2020-04-10T18:39:41.540037
Release Notes

CPU: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (2208 MHz)
Memory: 16231 MB
OS Version: Microsoft Windows 10 64-bit (Build 18362.778)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 1060/PCIe/SSE2

Windows Graphics Driver Version: 24.21.13.9835
OpenGL Version: 4.6.0 NVIDIA 398.35

Window size: 1920x1057
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.125
Render quality: 5
Advanced Lighting Model: Enabled
Texture memory: 512MB
VFS (cache) creation time: January 10 2020 13:16:53

J2C Decoder Version: KDU v7.10.4
Audio Driver Version: FMOD Ex 4.44.64
Dullahan: 1.1.1320 / CEF: 3.3626.1895.g7001d56 / Chromium: 72.0.3626.121
LibVLC Version: 2.2.8
Voice Server Version: Vivox 4.10.0000.32327

Packets Lost: 16/15,252 (0.1%)
April 15 2020 20:51:55

@sl-service-account
Copy link
Author

Maestro Linden commented at 2020-04-16T17:18:01Z

Hi Paige, thanks for the report. Could you please attach a copy of the script, or have the script creator do so? From the error message, it appears that the script is calling the llBase64ToInteger() function with bad input data. This could be a bug in the script API, or it could be caused by a bug in the script itself.

@sl-service-account
Copy link
Author

Lucia Nightfire commented at 2020-04-16T17:50:40Z, updated at 2020-04-16T20:00:26Z

llBase64ToInteger() seems to be having a "padding ignore" issue at first glance, but there is definitely a discrepancy between server versions.

[10:44:27] Lucia Nightfire: [10:39:25] Base642Int (539684): llBase64ToInteger("TQ==") = 1291909417(0x4d00f929)
[10:44:29] Lucia Nightfire: [10:43:43] Base642Int (540037): llBase64ToInteger("TQ==") = 1291845632(0x4d000000)

[EDIT]

 Is it me or does llBase64ToInteger() actually seem "fixed" or "correct" on 540037?

[EDIT]

From my chat history, I noticed that llBase64ToInteger() has been adding random numbers for the last two "unused" octets since 2016. I don't know how long its been doing that, how anyone could rely on that behavior without stripping it out, nor why I didn't file a bug report on that way back then either.

@sl-service-account
Copy link
Author

Maestro Linden commented at 2020-04-16T20:08:58Z, updated at 2020-04-16T20:21:58Z

Hi guys, we've investigated this issue some more. As [~lucia.nightfire] suggested, server version 2020-04-10T18:39:41.540037 includes a fix for a very old bug in llBase64ToInteger(), which would cause it to return unpredictable results for short input strings. With the fix, llBase64ToInteger() should return consistent results for any given input string. If the input string is not a valid base64 string (such as "" ) the function should now return 0 and print a warning message.

The script in the "LAQ Bento Mesh Head HUD v3.06" is almost certainly sending bad data to llBase64ToInteger(), triggering the new warning message. We're planning to hide this warning message, though it probably highlighting a bug in the script that triggered it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant