Awesome, thank you (knowing which is the problem extension will help us to figure out if we can work around it or if we'll have to tell people to disable that extension, etc)
Quick tip for narrowing it down more easily than just disabling them one at a time: let's say you have 20 extensions installed (just for easy explanation). Start by disabling #1-10 and see if you have the problem: if you do, the problem has to be one of those. (If not, it's with one of the ones in the #11-20 half of the list and you should test with those instead.) Disable half the remaining (so, #s 5-10), test again; if you still have the problem, the issue is with one of the 5 remaining. Disable 4 and 5, test again; if you still have the problem, the issue is with one of the 3 remaining. Etc.
When you hit the point where you aren't having the problem anymore, the issue is with one of the remaining extensions. So, if you disable 4 and 5 and the problem goes away, the problem is with one of those two. Disable 4, test, if you don't have the problem then it was #4; if you do have the problem, it was with #5. This way you can narrow it down more quickly!
It may also be that the issue is with an interaction of more than one extension. To disprove that: once you've got the suspected culprit, disable all extensions but that one, then test again. If the problem still happens, that's good: it means you've definitely found the extension that's causing the issues. (And please do let us know what it is so we can see if we can reproduce the problem ourselves, thus allowing us to work on fixing it!) If the problem doesn't happen with only that extension enabled, it's a conflict with multiple extensions behaving badly with each other, and you're going to have to do some more research, unfortunately.
At that point: enable the problem extension, then repeat the ever-narrowing exclusion tests you did in the first step (so if the problem extension was #4, start with #4 enabled, then #1-10 in addition and see if you have the problem, yadda, each time cutting the # of extensions you have enabled in half but making sure to keep the problem extension as one of them).
Before you do all that, you may want to rule out one more thing: it could be that NoScript is being weird. Try forbidding scripts to run from dreamwidth.org, then go back to NoScript's whitelist and add "dreamwidth.org" back to it (not www.dreamwidth.org) See if doing that helps to prevent the timeout problem?
no subject
Quick tip for narrowing it down more easily than just disabling them one at a time: let's say you have 20 extensions installed (just for easy explanation). Start by disabling #1-10 and see if you have the problem: if you do, the problem has to be one of those. (If not, it's with one of the ones in the #11-20 half of the list and you should test with those instead.) Disable half the remaining (so, #s 5-10), test again; if you still have the problem, the issue is with one of the 5 remaining. Disable 4 and 5, test again; if you still have the problem, the issue is with one of the 3 remaining. Etc.
When you hit the point where you aren't having the problem anymore, the issue is with one of the remaining extensions. So, if you disable 4 and 5 and the problem goes away, the problem is with one of those two. Disable 4, test, if you don't have the problem then it was #4; if you do have the problem, it was with #5. This way you can narrow it down more quickly!
It may also be that the issue is with an interaction of more than one extension. To disprove that: once you've got the suspected culprit, disable all extensions but that one, then test again. If the problem still happens, that's good: it means you've definitely found the extension that's causing the issues. (And please do let us know what it is so we can see if we can reproduce the problem ourselves, thus allowing us to work on fixing it!) If the problem doesn't happen with only that extension enabled, it's a conflict with multiple extensions behaving badly with each other, and you're going to have to do some more research, unfortunately.
At that point: enable the problem extension, then repeat the ever-narrowing exclusion tests you did in the first step (so if the problem extension was #4, start with #4 enabled, then #1-10 in addition and see if you have the problem, yadda, each time cutting the # of extensions you have enabled in half but making sure to keep the problem extension as one of them).
Before you do all that, you may want to rule out one more thing: it could be that NoScript is being weird. Try forbidding scripts to run from dreamwidth.org, then go back to NoScript's whitelist and add "dreamwidth.org" back to it (not www.dreamwidth.org) See if doing that helps to prevent the timeout problem?