I am not a politically correct person. Never have been, probably never will be. I simply state what I think and let people read it. With that said, please read this post with an open mind and read what it says, and don't infer any tones into it. It has no "tone" to the post and is not meant as a flame post.
Quote:
Originally Posted by gregt
 Maybe you should have said "you better be careful not to say it like an arrogant trouble maker, or they will think you are an arrogant trouble maker". |
Perhaps. The written language is more about the perception of the reader than of the writer. If people took it that way, then they took it that way. It wasn't meant that way. It was merely an observation of my own from reactions to being told there was a problem and conversations I have had with people on TRT (One of them a Mod).
Quote:
Originally Posted by gregt
No arrogant trouble maker tones there, eh? 
As with any new software, there are some bugs, they are being worked on, and any specific feedback we can get is helpful and appreciated. |
And I will give credit where credit is due. The CP does actually work better now. It is nowhere near as bad as it was even two days ago. And yes, it takes time to work out bugs but there has been a problem with the CP for almost 6 months now.
I opened the CP a few minutes ago to do the test listed below. It showed 43 threads. I browsed 15 of them, now it shows 19. There is still an issue but its getting a lot better.
Quote:
Originally Posted by Caball362
It is olny Arrogant if he could not back up what he says.
|
Quote:
Originally Posted by gregt
He doesn't have access to the code, nor memory on the servers TRT runs on.....
|
That is true, I don't have access to the server side code. But I wasn't referring to server side code, I was referring to the client side code for TRT. The client side code being the HTML, CSS and Javascript that the site uses that runs on the client. It can also include Java applets, Flash apps and some other things.
Want a simple test to see the memory issue?
Re-boot your PC.
Open your browser.
Open TRT.
Right click on the taskbar and pull up the Task Manager.
Go to the Processes tab.
Make note of the memory usage of the browser. Whether it be Firefox, Internet Explorer, Opera or Safari.
Browse thirty threads on TRT. Look again at the memory usage.
Open a second tab in the browser, close the TRT tab.
Look at the memory usage again.
It has gotten better since the upgrades to the CP but it is still there. It is a memory leak and it is caused by what is known in programming as a closure. A closure is when an object has a circular reference to itself. It is, predominantly, caused by anonymous functions in Javascript. There are other ways to create them but anonymous functions are the biggest cause of them.
The simplest analogy I can give for what a closure is is to think of a room full of people where people point at each other. Invariably, someone ends up pointing at themself. It isn't exactly what happens but it is close.
The only way to free up the memory that the closure uses is to close the browser. Simply closing the page won't free it up.
This is a link to the comp.lang.javascript Usenet group FAQ:
http://www.jibbering.com/faq/
This is a notes section written by Richard Cornford on closures:
http://www.jibbering.com/faq/faq_notes/closures.html
Richard was the Editor at one time of the FAQ, the new editor might be of interest to some people.
-Benjamin
