Cool VL Viewer forum

View unanswered posts | View active topics It is currently 2024-03-29 14:43:12



Reply to topic  [ 6 posts ] 
Crash Issues with Buffer Overload 
Author Message

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
Hello Henri,

Seems there is an issue with when I try TPing or logging into a sim I crash, or I don't crash right away. I keep seeing the same log entries for each session,

Code:
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 7 - Buffer size: 95 - Data size: 1916930592
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #2655
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 13 - Buffer size: 95 - Data size: 1884495973
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #25461
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 19 - Buffer size: 95 - Data size: 1953720174
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #26994
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 25 - Buffer size: 95 - Data size: 539369582
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #25957
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 31 - Buffer size: 95 - Data size: 541401189
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #26708
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 37 - Buffer size: 95 - Data size: 1952802162
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #29779
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 43 - Buffer size: 95 - Data size: 543452769
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #16928
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 49 - Buffer size: 95 - Data size: 543516756
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #8237
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 55 - Buffer size: 95 - Data size: 1411412837
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #26964
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::verifyLength: Buffer overflow in BinaryBuffer length verify, field name 'param_data' !  Current pos: 61 - Buffer size: 95 - Data size: 1765941364
2018-11-25T18:33:09Z WARNING: LLDataPackerBinaryBuffer::unpackBinaryData: Invalid data, aborting !
2018-11-25T18:33:09Z INFO: LLViewerObject::createNewParameterEntry: Unknown param type #24936

Log files: https://drive.google.com/file/d/1oGvogS ... sp=sharing
Seems I am the only one effected by this since it seems everyone else is using another viewer.

My viewer information
Code:
Cool VL Viewer v1.26.22.23, 64 bits, Nov 17 2018 10:11:09
Release Notes

You are at 2559091.8, 2560029.4, 22.0  in Commune located at
 (69.25.198.246:9119)
OpenSim 0.9.1.0 DreamNation 6df28342851d825ef4f0ce693d4e2fb52a86e8a8 2018-07-25 05:42:15 -0700 (Unix/Mono)

CPU: AMD Athlon(tm) II X4 640 Processor (3000.11 MHz)
Memory: 12288MB
OS version: Microsoft Windows 7 64 bits v6.1 (build 7601)
Memory manager: OS native
Graphics card vendor: NVIDIA Corporation
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2
Windows graphics driver version: 25.21.0014.1681
OpenGL version: 4.6.0 NVIDIA 416.81
Detected VRAM: 4096MB
J2C decoder: OpenJPEG: 1.4.0.635d
Audio driver: FMOD Studio v1.10.09
Networking backend: libcurl/7.47.0 OpenSSL/1.0.2l zlib/1.2.8
Embedded browser: CEF3 plugin v3.3325.1750.gaabe4c4
Packets lost: 4598/108581 (4.2%)

Built with: MSVC v1800

Compile flags used for this build:
/O2 /Oi /MD /MP /DNDEBUG /D_SECURE_SCL=0 /D_HAS_ITERATOR_DEBUGGING=0 /DWIN32 /D_WINDOWS /W3 /GR /EHsc /Oy- /GS /fp:fast /TP /W2 /Zc:forScope /Zc:wchar_t- /c /nologo /DLL_WINDOWS=1 /DUNICODE /D_UNICODE /DWINVER=0x0600 /D_WIN32_WINNT=0x0600 /DXML_STATIC /DBOOST_ALL_NO_LIB /DLL_LUA=1 /DLL_FMODSTUDIO=1 /DAPR_DECLARE_STATIC /DAPU_DECLARE_STATIC /DCURL_STATICLIB=1 /DLIB_NDOF=1


Hope this is actually a bug and not me. :lol:

Geoff


2018-11-25 19:00:00
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
This is caused by a crasher object, apparently... The log explains it all: invalid data is passed to the viewer by the sim.

Yet, it might be possible to avoid the crash and derender the object instead, but I need the crash dump file (CoolVLViewer.dmp) to spot the exact location of the crash and implement a workaround in the code...

Also, let me know if you have "Advanced" -> "Network" -> "Auto-kill bogus objects" checked or not, and if not, what happens if you check it ?

EDIT: I also went in the sim where you got your crashes, at the same position (among others), and TPed back and forth, without crashing ever. So I cannot reproduce your bug here and definitely need the crash dump file to go any further...


2018-11-26 01:14:56
Profile WWW

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
Hey Henri,

Sorry for getting back to you late. I don't have a crash dump file (CoolVLViewer.dmp) for that date. I went back to that location and after few minutes I crashed again and log shows the same info as before. No crash dump file was created. I only got "Cool VLViewer has stopped working" windows error.
Attachment:
Cool VLViewer has stopped working.PNG
Cool VLViewer has stopped working.PNG [ 34.77 KiB | Viewed 1908 times ]


I logged back in to the same location and did turn on "Auto-kill bogus objects" and I crashed again. No crash dump file was created and got the above error and same log entries as before.

Geoff


2018-11-27 21:35:30
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
It's not a viewer crash, then... This looks like a graphics driver bug... Turn off the Watchdog (in the Advanced menu), and see what happens.

Try updating (or downgrading) your graphics driver (if you recently updated it, it's probably the explanation for your issue).


2018-11-27 23:53:55
Profile WWW

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
HI Henri,

So Watchdog was already turned off. I did update my graphics card drivers but still crashing. :(

Geoff


2018-12-01 22:18:46
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
GeoffEarnshaw wrote:
I did update my graphics card drivers but still crashing. :(
I cannot reproduce the crash here, and since there is no crash dump, it means that the crash does not occur in the viewer itself. The usual suspects are: the graphics driver, the antivirus software, a virus...


2018-12-01 23:55:15
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 6 posts ] 

Who is online

Users browsing this forum: No registered users and 33 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.