Cool VL Viewer forum

View unanswered posts | View active topics It is currently 2024-03-28 18:05:19



Reply to topic  [ 10 posts ] 
Keep Crashing 
Author Message

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

Well I seem to be having issues, surprise :lol:

I have been crashing today when trying to login and thats after I crashed when I was on the DN grid. Not sure what the issue is. I'm sure its something to do with my computer however. Because I tried FS and it crashed on me too and said I had some sort of hardware configure issue. Not sure what it meant by that. I haven't done any software upgrades to my computer in weeks. But I did just update the GeForce graphics driver just now and I still crashed when trying to login. :( I looked in the logs and not sure what its telling me. I was hoping if you could tell me what the log says in plain English. :)

Here is my system info and log files.
Code:
Cool VL Viewer v1.26.20.30, 64 bits, Aug  5 2017 10:37:34
Release Notes

CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2592 MHz)
Memory: 16261MB
OS version: Microsoft Windows 8 64-bit  (Build 9200) compatibility mode. Real version: 10.0 (Build 10586)
Memory manager: OS native
Graphics card vendor: NVIDIA Corporation
Graphics card: GeForce GTX 970M/PCIe/SSE2
Windows graphics driver version: Loading...
OpenGL version: 4.5.0 NVIDIA 385.28
Detected VRAM: 3072MB
J2C decoder: OpenJPEG: 1.4.0.635d
Audio driver: FMOD Ex v4.44.64
Networking backend: libcurl/7.47.0 OpenSSL/1.0.1h zlib/1.2.8
Embedded browser: CEF3 plugin v1.5.3c-(CEF-WIN-3.2526.1347-32)

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_FMODEX=1 /DAPR_DECLARE_STATIC /DAPU_DECLARE_STATIC /DCURL_STATICLIB=1 /DLIB_NDOF=1



Also, I just checked the Windows Event Viewer after I just posted the above and saw this:
Event 1000, Application Error
Code:
Faulting application name: CoolVLViewer.exe, version: 1.26.20.30, time stamp: 0x598586e3
Faulting module name: CoolVLViewer.exe, version: 1.26.20.30, time stamp: 0x598586e3
Exception code: 0xc0000409
Fault offset: 0x000000000153b8c0
Faulting process id: 0x3eec
Faulting application start time: 0x01d316b4292dfe91
Faulting application path: D:\Program Files (x86)\CoolVLViewer-1.26.20\CoolVLViewer.exe
Faulting module path: D:\Program Files (x86)\CoolVLViewer-1.26.20\CoolVLViewer.exe
Report Id: a6f6d12f-768d-4ad9-86da-3d3c0fbaba53
Faulting package full name:
Faulting package-relative application ID:


Thank You!

Geoff


Attachments:
debug_info.log [1.57 KiB]
Downloaded 163 times
CoolVLViewer_2104.log [23.91 KiB]
Downloaded 167 times
2017-08-16 17:43:57
Profile

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
OK I might have fixed the issue. I had forgot the other day I enabled "Allow HTTP pipelining in OpenSim grids". I remember this just now and disabled it. So far I was able to login and haven't crashed yet! cross my fingers.

Geoff


2017-08-16 18:19:17
Profile

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
Never mind, had the same issue, but this time the log file grew to 98.6 MB :shock:

Takes awhile to open this file.
https://drive.google.com/open?id=0B9sV-iciXiMUU3dPTjc4V3F0TEk

I think I might try the previous version of CLV.

Geoff


2017-08-16 18:40:10
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
That setting is very unlikely to have anything to do with your crashes (I just logged in in Dream Nation with HTTP pipelining enabled and I did not crash), even if pipelining is probably not yet implemented in OpenSim grids.

It could be a driver issue that got triggered by a specific object. Without the dump file (CoolVLViewer.dmp file, in the same directory as where the logs are stored), I cannot tell where the viewer crashed exactly. So, next time, please do provide this file in excess of the corresponding CoolVLViewer_NNNN.log file...


EDIT:
Quote:
Never mind, had the same issue, but this time the log file grew to 98.6 MB
Yep, that's a (bunch of) crasher object(s), or invalid UDP messages sent by the sim... Try enabling the KillBogusObjects debug setting before logging in, and see what happens. Also, please, send me the grid coordinates (sim name) of the crash.


2017-08-16 18:42:34
Profile WWW

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
Well I do not have current CoolVLViewer.dmp file for the crashes. Seems Windows 10 is automatically closing the viewer when it crashes.
Attachment:
CLV has Stopped working.png
CLV has Stopped working.png [ 47.98 KiB | Viewed 2992 times ]


I did enable the KillBogusObjects debug and I am on for the time being. I also sent you a LM where the crashes where happening inworld.

Geoff


2017-08-16 22:00:48
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
GeoffEarnshaw wrote:
Well I do not have current CoolVLViewer.dmp file for the crashes. Seems Windows 10 is automatically closing the viewer when it crashes.
No, it closed it before it actually crashed (and it would probably not have crashed at all without Windoze's stupid assumption), probably as a result of graphics driver "freeze" or large delay in returning from a call... Please, provide the log.

Quote:
I did enable the KillBogusObjects debug and I am on for the time being. I also sent you a LM where the crashes where happening inworld.
Well, I'm not crashing there, with KillBogusObjects enabled... However, I do see a massive slow down in the fps rate (from 50+ to 8-10fps !) when facing the lagoon with a 512m draw distance, from the LM point you gave me: on a weaker system than mine (Linux desktop PC with a 4.6GHz Core-i5 2500K and a 1.5GHz GPU/4GHz VRAM GTX 970), it could definitely bring your video card to its knees and look like a "problem" for that Mickey Mouse OS which is Windows... What is your draw distance ?


2017-08-16 23:10:24
Profile WWW

Joined: 2014-09-25 22:10:40
Posts: 135
Location: Colorado
Reply with quote
OK, so here are the logs, including the not current *.dmp files I have in the logs folder.
https://drive.google.com/open?id=0B9sV-iciXiMUZFdNcXhtMlhfdWc

My draw distance is set at 128m. My FPS is always between 5 and 15 fps. Jumps around a lot and It has always been that way and I figure its because of OpenSim. I do have a GTX 970M however.

And it does appear that enabling the KillBogusObjects debug has worked.

Thank you for helping me. :)

Geoff


2017-08-17 01:12:30
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
GeoffEarnshaw wrote:
OK, so here are the logs, including the not current *.dmp files I have in the logs folder.
Alas, this dump file does not correspond to the current version (v1.26.20.30), so it is of no use at all for me.

Quote:
My draw distance is set at 128m. My FPS is always between 5 and 15 fps. Jumps around a lot and It has always been that way
That's pretty low...

Quote:
I figure its because of OpenSim.
Well, mega regions are fps killers, but otherwise, OpenSim is the same as SL for fps rates...

Quote:
I do have a GTX 970M however.
Which got about half the performances of a non-overclocked GTX 970... Mobile GPUs are not great performers, and neither are mobile CPUs...

Quote:
And it does appear that enabling the KillBogusObjects debug has worked.
Keep it on: I'll make it the default for next release. It'd be interesting to know what are those bogus objects however, and to understand why they are bogus... You will find their UUID in the viewer logs, so you could tell about them to the sim owner.


2017-08-17 07:40:45
Profile WWW

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

So the sim is not a mega region (varrigion) but a 256x256 sim. I basically the owner of the sim, well part owner. Almost everything you see I placed there. Never had any issues with any of the items in the past. But I am trying to identify the objects in the log, UUID in the search isn't having much success. However, we think there was an issue with the robust and asset server yesterday. They will be investigating the issue to see what happened, if there was an issue that is.

Geoff


2017-08-17 18:06:01
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
GeoffEarnshaw wrote:
I am trying to identify the objects in the log, UUID in the search isn't having much success.

The culprit items get derendered by the viewer when KillBogusObjects is TRUE, so they won't appear in the "Area search" floater...


2017-08-17 19:09:40
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 10 posts ] 

Who is online

Users browsing this forum: No registered users and 24 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:  
cron
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.