(actual test) Filetrip related test

[The Catboy]

@smileyhead and or @Yandere-chan Please clear your caches. This thread does not contain any previous comments on mine or filetrip links.

Due to the issue brought up in this thread, I've made this thread as a test thread in an attempt to help narrow down the problem. This is not a standard EOF thread, but more so a troubleshooting thread, please do not treat this like a normal EOF.

 

[smileyhead]

@smileyhead and or @Yandere-chan Please clear your caches. This thread does not contain any previous comments on mine or filetrip links.

no change.

 

[The Catboy]

no change.

What about with a different browser?

 

[smileyhead]

What about with a different browser?

no warning on Edge

 

[The Catboy]

no warning on Edge

Are you sure you cleared the cache on the previous browser? Does it still happen after you close the browser?

 

[smileyhead]

Are you sure you cleared the cache on the previous browser? Does it still happen after you close the browser?

yes.

 

[The Catboy]

yes.

How many browsers have you tested this on?
I am at the mercy of the community here because none of mine have been effected by this
Oh, do you have adblock installed?

 

[smileyhead]

How many browsers have you tested this one?

Chrome Stable (Desktop, latest, x64)
Chrome Beta (Android, latest, ARM)
Microsoft Edge (Desktop, latest, x64)

Oh, do you have adblock installed?

yes, but

1. I have it disabled on 'Temp.
2. I don't need it anyway, since I'm a Patron.

 

[The Catboy]

Chrome Stable (Desktop, latest, x64)
Chrome Beta (Android, latest, ARM)
Microsoft Edge (Desktop, latest, x64)

yes, but

1. I have it disabled on 'Temp.
2. I don't need it anyway, since I'm a Patron.

I wonder if it is caused by the ads because I am not getting this on my iPhone nor my Android phone.
Thanks, if I can think of anymore test or y'all have any tests, please try to keep them here.
As well this is not a standard EOF thread, please keep this thread on topic.

 

[Deleted User]

Haven't got the error on this thread yet, but have gotten it a few times on the main thread.

 

[The Catboy]

Haven't got the error on this thread yet, but have gotten it a few times on the main thread.

I am 80% sure that might be a cache error. That's why I made this thread to test that.

 

[Issac]

No problems for me in this thread on my desktop, with Chrome. Going to Filetrip still gives me a red screen and such, but this thread does not. Neither does the original thread.

Still going around trying to find filetrip hosted images to see if that still is an issue.

 

[The Catboy]

No problems for me in this thread on my desktop, with Chrome. Going to Filetrip still gives me a red screen and such, but this thread does not. Neither does the original thread.

Still going around trying to find filetrip hosted images to see if that still is an issue.

Fantastic, now let's see what happens when I post this

 

[Issac]

Red screen!

 

[The Catboy]

Red screen!

Cool, so we can officially deduce that my signature was the cause of the red screens in the other threads. My signature was hosted on filetrip, thus was causing the issue.

 

[Deleted User]

Cool, so we can officially deduce that my signature was the cause of the red screens in the other threads. My signature was hosted on filetrip, thus was causing the issue.

Can also confirm the other thread has been tainted. Atleast we figured out whats wrong XD

 

[The Catboy]

Can also confirm the other thread has been tainted. Atleast we figured out whats wrong XD

The thread itself wasn't tainted, I was the tainted one. I use filetrip to host my signatures, so every post of mine with the exposed signature resulted in a red screen. Switching to a different source corrected that issue.
Which is good because I nearly 20,000 posts, not including the uncounted ones. So chances were extremely high that someone was bound to run into one of my posts and get a red screen.

 

[Noctosphere]

what are we talking about here? maybe i can help testing?

 

[smileyhead]

what are we talking about here? maybe i can help testing?

you should've read the thread, lad. (wew, dat rhyme tho)

testing's finished. we were testing what causes Chrome to recognise a thread on here Dangerous. it was Lilith's sig.

 

[Deleted User]

Oh thanks, now this "dangerous" tag will be stuck everywhere on temp for me.