NIT ERROR: Error: INDEX_SIZE_ERR: DOM Exception 1 - Userscripts.org

Signup
Login

THE Jawz's KabaListics (the Original script)

By Jawz74 — Last update Jan 6, 2013 — Installed 606,011 times.

NIT ERROR: Error: INDEX_SIZE_ERR: DOM Exception 1

in
5 posts, 2 voices

Dec 28, 2011 1:47am Тim Οmaha User	Getting an error "NIT ERROR: Error: INDEX_SIZE_ERR: DOM Exception 1" At the bottom of the screen. The background of the tool is transparent and the formatting appears to be messed up. I attempt to get to the options setting to turn on the log tab and detailed logging but it won't retain any changes. I really don't know what the cause is. I'd hazard a guess, is the script running out of local storage? ... Just cleared the local storage for the particular realm that was having problems and things went back to normal, except, of course, all my settings and data were wiped out.

Dec 28, 2011 8:06am Jawz74 Script's Author	Yep, this is a local storage issue. You reached the limit (5Mo). So Probably, you are using chrome or FF with multiple accounts in the same browser. Try to use Chrome and to define one profile per realm/account. Like that, you will have one distinct local storage of 5M per account/realm.

Dec 28, 2011 3:00pm Тim Οmaha User	Using Chrome here and only one realm on my laptop which is the only place I have KabaListics installed as well. I do, however have the teamwork script installed as well which may contribute to the problem. Sounds like it'll be one chrome profile per realm and only one script. I know this is a terrible question to ask, but, is there any way around the local storage limitation? I set the script to do a map scan last night before I went to bed and it still has not completed, so I'm thinking I'll need to wipe it clean again, and just make a separate bare bones chrome profile for each realm?

Dec 28, 2011 3:58pm Jawz74 Script's Author	I don't know if the 5Mo limitation is for one chrome occurence or per script... Anyway, it should be better to have one profile per script. For the map scan, I think you should use at 21 radius maximum. As it manage a lot of data, maybe the script rans out of local storage space... Concerning the storage limitation, I know there's a way to increase it but I don't know how to do it. And it seems that this may be risked.

Dec 28, 2011 4:06pm Тim Οmaha User	Perhaps the script can be packaged as a chrome extension. I don't know a whole lot about it, but there seems to be a permissions option that will allow for unlimited storage. http://code.google.com/chrome/extensions/manife... Kinda seems as if the complexity of this script has almost outgrown the limitations of JS and you could make some good use of some of google APIs, perhaps.

Voices