SABnzbd Forums

I have a problem with SABnzbd+ 0.5.0 RC3 + Plush + Chrome 4.0.249.78: when I start SABnzbd+, it cannot display the download queue and the download history (as it is standard in Plush), but it shows two progress indicators which turn clockwise and it hangs there.

Opening it in Firefox does not give any problem, it works perfectly. So I guess this is a problem of SABnzbd+ and the current version of Google Chrome.

Sorry,  no problems here with that combination.
(RC3, Chrome 4.0.249.78 on Win7 64bit).

33 pages of history and 15 jobs in the queue.

Well, I also use SpywareBlaster and SpyBot (I have immunized my system with both programs), so maybe they block some cookie needed for loading Plush.

I use Windows 2003 R2 SP2 x64.

I also have the following lines in my hosts file:

127.0.0.1 adserver.adtech.de #speed up expatica.com
127.0.0.1 www.adserver.adtech.de #speed up expatica.com
127.0.0.1 stat.onestat.com #speed up romanians.nl
127.0.0.1 www.stat.onestat.com #speed up romanians.nl
127.0.0.1 onestat.com #speed up romanians.nl
127.0.0.1 www.onestat.com #speed up romanians.nl
127.0.0.1 integrare.kestionare.ro #speedup rombel
127.0.0.1 www.integrare.kestionare.ro #speedup rombel
127.0.0.1 kestionare.ro #speedup rombel
127.0.0.1 www.kestionare.ro #speedup rombel
127.0.0.1 trafic.ro #speedup rombel
127.0.0.1 www.trafic.ro #speedup rombel
127.0.0.1 ts2.trafic.ro #speedup rombel
127.0.0.1 www.ts2.trafic.ro #speedup rombel
127.0.0.1 ts.trafic.ro #speedup rombel
127.0.0.1 www.ts.trafic.ro #speedup rombel
127.0.0.1 ts1.trafic.ro #speedup rombel
127.0.0.1 www.ts1.trafic.ro #speedup rombel
127.0.0.1 nl.sitestat.com #disable tracking cookies
127.0.0.1 www.nl.sitestat.com #disable tracking cookies
127.0.0.1 sitestat.com #disable tracking cookies
127.0.0.1 www.sitestat.com #disable tracking cookies
127.0.0.1 quantserve.com #disable tracking cookies
127.0.0.1 www.quantserve.com #disable tracking cookies
127.0.0.1 bluestreak.com #disable tracking cookies
127.0.0.1 www.bluestreak.com #disable tracking cookies
127.0.0.1 doubleclick.net #disable tracking cookies
127.0.0.1 www.doubleclick.net #disable tracking cookies
127.0.0.1 fastclick.net #disable tracking cookies
127.0.0.1 www.fastclick.net #disable tracking cookies
127.0.0.1 apmebf.com #disable tracking cookies
127.0.0.1 www.apmebf.com #disable tracking cookies
127.0.0.1 statcounter.com #disable tracking cookies
127.0.0.1 www.statcounter.com #disable tracking cookies
127.0.0.1 tradedoubler.com #disable tracking cookies
127.0.0.1 www.tradedoubler.com #disable tracking cookies

My DNS service is set on automatic.

My IPv6 helper service is set on disabled.

I do not have Java installed.

Any warnings in the javascript console (Ctrl+Shift+J)?

Is javascript enabled? Options > Under the Bonnet > Content Settings > Javascript (Although this option dialog looks broken).

Can you view http://localhost:8080/queue/ and http://localhost:8080/history/ (they won't look pretty, but should not show any red errors)

I deleted and then reinstalled Chrome, after cleaning all Chrome traces from my Local Settings profile, and now it works ok with SABnzbd+.

So, it was due to some peculiarity of my Chrome installation, and it can be closed as a SABnzbd+ bug report.

almodovaris wrote: I deleted and then reinstalled Chrome, after cleaning all Chrome traces from my Local Settings profile, and now it works ok with SABnzbd+.

So, it was due to some peculiarity of my Chrome installation, and it can be closed as a SABnzbd+ bug report.

Someone else had an issue like this recently, it ended up being a cache / cookie issue.

I believe it is a chrome bug, specifically this one: http://code.google.com/p/chromium/issue ... l?id=23499

I think I know the cause: I used Clamav to scan my computer. Clamav thinks that plush.js is malware, therefore it removes this file. In general, Clamav thinks that the installation package of SABnzbd+ contains malware (SQL injection or something like that).

An extra update on this topic: having reinstalled SABnzbd+ and therefore having restored Plush.js, Google Chrome still had the reported problem, but Firefox worked fine with SABnzbd+.

I think the cause are some false positive deletions done by ClamAV, see the attached file.