Journal davidsyes's Journal: Slashdot crashes my Opera Browser 2
This is what i'm going to submit to Opera. I declined to let the crash reporter send the log, as it had information not only about my visited sites, but file paths in the two machines on which i could repeatedly duplicate the crash.
But, Slashdot might want to cooperate with Opera. However, anyone searching for this bug will find on the bug report page:
"Note: Due to the sensitive nature of the data in our tracking system, no public list of known bugs is available." It still might be under discussion, though.
Opera 10.00 Beta 2 Build 1642 summarily crashes if simply double-tap "A" in Ctrl+A at the site www.slashdot.org.
First, pick a comment and hit reply (i did it as a logged-in user; dunno if it'll work as an anonymous commenter). Then click outside of the comment reply box. THen rapidly click the "A" in Ctrl+A keystroke. BOOM, it crashes.
Repeated on two different Dell desktops, one over 8 years old with ~ 1GB RAM (and over 20 tabs open), the other around 3 years old with 2+GB (and around 7 tabs open), Machines' OS: XP Pro.
Another way to crash it it anonymously at Slashdot, click on "Login", but don't log in. Just click outside the login popup, then double-tap the "A" in Ctrl+A.
(Dammit, we need a free-entry Journal Topic field.... Opera's not in the drop-down list.)
Looks like the crash log tool is the only easy way (Score:1)
to send them crash/bug information.
Slashback? (Score:1)
I tend to use slashback when documenting slashdot bugs in my journal.
I didn't see a slashdotbug entry in the drop down.