Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

•Re: Problems with recent PM update and Safari

by merlyn (Sage)
on Oct 03, 2003 at 21:23 UTC ( [id://296397]=note: print w/replies, xml ) Need Help??


in reply to Problems with recent PM update and Safari

I'm replying to my own note with a sniffer turned on, to see if I can trigger another crash. I'm torn as to whether I want it to crash this time or not. {grin}

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.


update: and yes, this note made it crash, but when I saved the reply to this note locally, including the CSS also fetched, it didn't crash anything. {sigh} I don't know where to go next.
  • Comment on •Re: Problems with recent PM update and Safari

Replies are listed 'Best First'.
Re^2: Problems with recent PM update and Safari (next)
by tye (Sage) on Oct 04, 2003 at 06:46 UTC

    Things I'd try next (since it sounds like it will be an on-going annoyance, to say the least):

    1) Try posting an anonymous reply using an otherwise identical setup.

    2) Try your account on someone else's copy of Safari. You could do this by loaning someone you trust your password or getting someone to loan you their computer.

    3) See if POSTing is part of the problem. Change www.perlmonks.org (or whatever) in your hosts file to localhost and write a quicky web page (or web server) that will deliver a copy of a PM page, accept your reply submission, and deliver the copy of what PM gives back. If that doesn't trigger the problem, then consider sacrificing a few chickens. If it does trigger the problem, then you've built a perfect lab for figuring out exactly which changes prevent the problem.

    As for things that changed at PM in the last while, I didn't have too much trouble finding pages from a few weeks or months ago in my browser cache. My files won't match your setup, but you might also be able to find such.

    Then, of course, there are the standard things that I often call "voodoo" debugging, that is, changing any number of things that may or may not be related hoping to make the problem go away (user settings, upgrade the browser, flush cache [though I might actually try that one at some point], ...), but I usually prefer to identify the problem...

                    - tye

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://296397]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chanting in the Monastery: (3)
As of 2024-04-19 15:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found