Why is 3.1 locking up and all it will do is houerglass my cusor? I have to click the X in the top right of the window to make it stop. The first version kept track of new software added to workstations and the newer ones don't do so well. While I realize that as bugs are fixed, it should be getting better. Why do I find new problems with each new release.

I have noticed the same thing the last couple of days. But, I am not sure if I am running 3.1. I just got the announcement today, but I did reinstall the application two days ago because it had crashed and refused to run yet again. So I may be running 3.1

Anyway, it is more pronounced in Firefox 3, but the application whill show the hourglass for a while (20 seconds or so) after clicking on something. I tried in IE 6 and the delay is significantly reduced, but still present.

You can use the Adblock Plus drop-down menu to turn off blocking for a particular domain. Since the ads load in an iframe, you might need to right clear in the right ad sidebar and open in a new window to get the right server to show up in the Adblock Plus drop-down.

So your saying that was unintentional? I just assumed that an ad-supported piece of software doing a little counter-spy work to make people disable their ad blockers would have been pretty high on your funding providers priority list! :)

Why is 3.1 locking up and all it will do is houerglass my cusor? I have to click the X in the top right of the window to make it stop. The first version kept track of new software added to workstations and the newer ones don't do so well. While I realize that as bugs are fixed, it should be getting better. Why do I find new problems with each new release.

It was completely unintentional and once we realized the problem, we fixed it immediately (you will see this fix in the next release).

With new features comes new bugs and in 3.0 we added *MANY* new features. We tried very hard to test/fix as many bugs as we could but there is so many varied network configurations among our user population that is is inevitable that some bugs will slip through the cracks. In the upcoming major release we are focusing more on fixing bugs/simplifying usage and less on adding major new features.

1st Post

I'm experiencing these issues with 3.1 currently, however, I am not running Ad blocking software on the windows XP machine that I'm using. Currently, I'm running a 1.7GHz P-4 with 256MB of RAM. I know the RAM is low, but it shouldn't be so bad that it takes 20 minutes and still nothing happens. And when the amount of RAM taken up is only 50MB-75MB, I doubt there is a RAM problem.

So far, I've tried dropping the Windows Firewall as well as turning off any anti-virus utilities. I've tried using IE 8 as well as Firefox 3.03. I've restarted my computer as well as reset the service.

It worked for me once and I've gotten to the console a couple times. I managed to kick off an inventory sweep once but I can't figure for the life of me why this is running so slow.

1st Post

Tzonarin, what you are describing does sound like the same issue as the one described in this thread, but I could be wrong. It's not so much a slowness issue that ADP introduces as much as a "locking you out of the app for 20 seconds" problem.

Is the machine you described dedicated to Spiceworks? Meaning no other services are running and no users login to that machine? If yes, then I guess it should be fine but 256 MB RAM is incredibly small and doesn't even meet the minimum requirements of 512 MB or more. If there is a scan running, and you are also using a memory intensive portion of the application such as running reports or browsing a large collection of software, you will ABSOLUTELY max out your memory, causing lots of paging to occur (memory to disk transfer) which will greatly slow Spiceworks down.

Tom, we thought we fixed this issue with the ad blocker. What version are you running? We tested in both Firefox 2 and 3 and verified it to be fixed a long time ago.

Since this post, I've upgraded the RAM of this machine to 512MB, thinking that maybe was the case. However, I am still experiencing this error and even in a scanning situation, there is still memory left over, so the machine isn't RAM starved now - but yet, it still hangs. I've even left it overnight and saw no progress on the start up bar, even trying to restart the SpiceWorks daemon, the computer, and reinstall the software outright.

This machine is a simple XP workstation and only serves as my management station for the network, so it's not that the machine is too overly busy or anything.

Please PM me or start a new thread about this issue. It sounds like you have some unique problems compared to the other folks in this thread. I do not want to sidetrack this topic since it is about AdBlocker Plus causing issues.

also tried using chrome real quick and had some similar issues with it (no plugins installed at all). it didn't end up as busy as often as ff but also every second or third page, whereas in ff it happens for every single page.

There has got to be something that is being blocked here, because other than people running AdBlcoker, we have never seen this issue.

To explain what's going on, the first time a Spiceworks page loads for you, we use JavaScript to detect your screen resolution and we send (via Ajax) this information back to your Spiceworks application (from the browser) so that it remembers it for the rest of your session. This information is used to determine if you should get the normal layout of the application or the narrow version.

If the Ajax request that sends the screen resolution is blocked (or has an exception for some reason), then you will experience this screen resolution detection on every page load.

Well, that's something to consider. One thing that I do is I often with use Remote Desktop Connection to communicate with my install which might be an interesting clue. Maybe bringing graphics adapters into the equation may help in helping understand what this problem is...