Changes between Initial Version and Version 1 of Ticket #12842, comment 2
- Timestamp:
- Jul 22, 2014 3:47:15 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12842, comment 2
initial v1 1 Two or three users have now reported the same error , they also report that reverting to 4.3.6 fixes the issue.1 Two or three users have now reported the same error in recent months, they also report that reverting to 4.3.6 fixes the issue. 2 2 3 For example: https://forums.virtualbox.org/viewtopic.php?f=6&t=62700. 3 For example: https://forums.virtualbox.org/viewtopic.php?f=6&t=62700. This is with Win7 as host and guest. VBox 4.3.14. 4 4 5 I have checked what I thought were obvious causes, by I couldn't find that UTF16 was being used at all, never mind with invalid codes. It looks like a parsing error introduced in 4.3.8, and still there in 4.3.14.5 After each report I have checked what I thought were obvious causes, by I couldn't find that UTF16 was being used at all, never mind with invalid codes. It looks like a parsing error introduced in 4.3.8, and still there in 4.3.14. 6 6 7 7 Apparantly the error appears before the log is created, so the above thread includes a log file from 4.3.6 and doesn't show the error. Useful for getting some context though. 8 9 None of those affected (apart from the OP) seem to be interested in raising ticket, being happy with the 4.3.6 workaround, so I thought I should do the honors.