Anonymous | Login | Signup for a new account | 2019-12-10 14:22 PST | ![]() |
Main | My View | View Issues | Change Log | Roadmap | Summary | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0008564 | opensim | [REGION] Script Functions | public | 2019-07-18 23:15 | 2019-07-31 18:38 | ||||
Reporter | tampa | ||||||||
Assigned To | tampa | ||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | master (dev code) | |||||||
Summary | 0008564: Simulator uptime through ossl | ||||||||
Description | Either expanding the osGetRegionStats() function with a STATS_SIM_UPTIME part or adding a osGetSimUptime() to fetch the simulator uptime as there is a console function for this already implemented and knowing(showing off) the uptime might be desireable for statistical analysis and testing stability over time. | ||||||||
Additional Information | I noticed that a simulator that has been running idle for months now suddenly jumped in memory usage from 2-4gb to 8gb as of this posting. It has been running 165 days now. A hint to a potential memory leak, though I would say running a sim that long is not normal either. Does show how stable we have gotten though :) | ||||||||
Tags | No tags attached. | ||||||||
Git Revision or version number | |||||||||
Run Mode | Grid (1 Region per Sim) , Grid (Multiple Regions per Sim) | ||||||||
Physics Engine | Other | ||||||||
Script Engine | |||||||||
Environment | Mono / Linux64 | ||||||||
Mono Version | 5.x | ||||||||
Viewer | |||||||||
Attached Files | |||||||||
![]() |
|
(0035520) UbitUmarov (administrator) 2019-07-31 06:38 |
added "region_up_time" to llGetEnv returns a string with seconds since region start that string represents a integer to get a number just do: integer uptime = (string)llGetEnv("region_up_time"); this could had been done using current api, but ok |
(0035530) tampa (reporter) 2019-07-31 18:38 |
I know there are other ways, but this is simpler and likely more reliable. Thanks for adding it, much appreciated! |
![]() |
|||
Date Modified | Username | Field | Change |
2019-07-18 23:15 | tampa | New Issue | |
2019-07-31 06:38 | UbitUmarov | Note Added: 0035520 | |
2019-07-31 18:38 | tampa | Note Added: 0035530 | |
2019-07-31 18:38 | tampa | Status | new => resolved |
2019-07-31 18:38 | tampa | Fixed in Version | => master (dev code) |
2019-07-31 18:38 | tampa | Resolution | open => fixed |
2019-07-31 18:38 | tampa | Assigned To | => tampa |
Copyright © 2000 - 2012 MantisBT Group |