A very... weird bug.

[Chronosplit]

I have no idea why this happens but I've tried multiple times after refreshing, emptying my cache, and restarting my browser. Bear with me because this is a weird situation. I'm using Chrome, latest Mac version.

In a very specific thread, right when I go to the bottom of someone in particular's posts right before the sig, my browser hangs and never will go forward, to the point that it asks to kill the window.

Here's the thread. On this specific page the first poster is the one I'm talking about. Does anyone else have any problem? Is it just my fault for some unexplainable reason?

 

[bobandbill]

My unhelpful response is that I am not getting the same problem as you - I get to the bottom of each post including the first just fine.

Do you get the same error after resetting your browser/clearing cookies, or on a different browser/computer?

 

[Satoshi Ookami]

It happens on Chrome sometimes (on different threads, though)... you either need to kill Chrome and try again or open the specific page with Firefox or something.

 

[Rukario]

can you post the link to the post that you think is causing it (its that number in the upper right corner of each post) your threadview link with page #'s doesn't work for users that show more or less then the default number of posts per page.
thanks

 

[Elaitenstile]

Just checked it and I got the same bug. Except I could kill it with closing two tabs. I think there must be some kind of overload or something in that page, because my internet is not very fast.

But I can't help you out here, I just got the bug as well.

 

[Chronosplit]

My unhelpful response is that I am not getting the same problem as you - I get to the bottom of each post including the first just fine.

Do you get the same error after resetting your browser/clearing cookies, or on a different browser/computer?

Every time using Chrome on all of those instances, now that I've been able to try it on a different comp.

It happens on Chrome sometimes (on different threads, though)... you either need to kill Chrome and try again or open the specific page with Firefox or something.

I just tried it on Firefox, it's working so far. I've never had this kind of problem on any thread or post except for where I mentioned specifically.

can you post the link to the post that you think is causing it (its that number in the upper right corner of each post) your threadview link with page #'s doesn't work for users that show more or less then the default number of posts per page.
thanks

This is the first instance on the page I linked: https://www.pokecommunity.com/posts/7868226/
Sorry about that, I wasn't really able to even get to the links for those up until now. XD

There are a few extra things I'd like those affected to try.

First, view the page again and see if the issue continues.
If it persists, head into your User CP and disable signatures, avatars, and images.
If the issue stops, enable avatars and images. If the issue doesn't continue, enable signatures once more.

Singling out things we can deal with helps a lot.

I just disabled all three and tried it, it just results in a white screen and the page still hanging up. I refreshed this page to make sure it just wasn't the site wigging out.
EDIT: no, I think it was just the site. It loaded when I tried a second time, but still I needed to kill it all the same.

I'll try with various combinations here in a second.

EDIT:
With only sigs- Hangs up all the same.
With only Avies: Hangs
With only images: Still hangs.

I'm not sure what's going on, but I don't think looking at this that it's image overload.

 

[MKGirlism]

I just tested it on a Mac with OS X Mavericks and the latest Google Chrome Dev Build.
Nope, it didn't happen to me, it must be your problem then.

 

[donavannj]

It was happening for me on Chrome until recently. The only thing that changed was that I installed a script blocker, but it still caused an app hang the first session I visited the page and decided to enable some of the scripts. I think it was one of the ad scripts that led to the crash, but I haven't been able to replicate the issue since on that particular page linked in the OP.