View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000037 | Asuna | [All Projects] General | public | 2018-09-28 02:29 | 2020-01-29 00:40 |
| Reporter | kyle | Assigned To | kyle | ||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | suspended | ||
| Summary | 0000037: Crash on SQL (Weird names) | ||||
| Description | Asuna crashed after getUserDatabaseID | ||||
| Steps To Reproduce | N/A | ||||
| Additional Information | 2018-09-27 13:19:56 [JOIN] Client Move Event: Start [Client ID: 42 ] - Visib: 0 - New Chan: 12382 :: Old Chan: 0 2018-09-27 13:19:56 [JOIN] Client Move Event: Checking Username 2018-09-27 13:19:56 [JOIN] Client Move Event: Checking Username - ër 2018-09-27 13:19:56 [SECURITY] Checking username: ër 2018-09-27 13:19:56 [SECURITY] Username OK. 2018-09-27 13:19:56 [JOIN] Client Move Event: Username OK. 2018-09-27 13:19:56 [JOIN] Client has joined TeamSpeak. Running SQL Check. 2018-09-27 13:19:56 [PLUGIN] getUserDatabaseID Success! | ||||
| Tags | No tags attached. | ||||
|
|
This may not be anything, but I may need to add checks for weird usernames as this may indicate memory corruption which could be causing the crashes. I don't see anyone that possibly has that username so this is probably indicating an issue with memory handling in TeamSpeak |
|
|
This bug seems to have been fixed as Asuna hasn't crashed from a weird name. Also due to the recode I'm resolving this bug as it's so old. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-09-28 02:29 | kyle | New Issue | |
| 2018-09-28 02:29 | kyle | Status | new => assigned |
| 2018-09-28 02:29 | kyle | Assigned To | => kyle |
| 2018-09-28 02:31 | kyle | Note Added: 0000079 | |
| 2020-01-29 00:40 | kyle | Status | assigned => closed |
| 2020-01-29 00:40 | kyle | Resolution | open => suspended |
| 2020-01-29 00:40 | kyle | Note Added: 0000086 |
