Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Problems with recent PM update and Safari

by merlyn (Sage)
on Oct 03, 2003 at 20:54 UTC ( [id://296391]=monkdiscuss: print w/replies, xml ) Need Help??

Recently, almost every reply-post I've made (although not a later re-edit) has caused my Safari browser to crash. Is anyone else here using a red theme (if that makes any difference), the default CSS, and Safari, and can confirm or deny crashes on replies?

It's definitely something in the reply HTML, because the reply is always successful... the crash happens while trying to re-render the page.

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

update: in fact, the browser crashed right as I submitted this note, but not the subsequent edits!
  • Comment on Problems with recent PM update and Safari

Replies are listed 'Best First'.
(wil) Re: Problems with recent PM update and Safari
by wil (Priest) on Oct 04, 2003 at 07:13 UTC

    This keeps happening to me, too. When I want to reply to a PM post I have to switch to Mozilla or IE.

    I'm running Safari 1 (85.5) and default CSS, default theme, default everything.

    It only seems to happen to me on this site, too, so I don't know what to make of this as a bug in Safari.

    Update: If it makes a difference, I usually preview my messages and then post. Not sure if the HTML is different on those two forms.

    - wil
      I apologize for the vagueness ahead of time, but as a web guy I remember testing some DHTML/CSS stuff back in the spring, when Safari was still "beta", and noted some incompatibilities. Here's the vague part, I don't remember what was causing the problems.

      I have no idea what the Perl Monk's CSS looks like, but here's a relatively recent chart of CSS compatibility, for what it's worth. Also some helpful links there.

      Gotta love them browser standards!

•Re: Problems with recent PM update and Safari
by merlyn (Sage) on Oct 03, 2003 at 21:23 UTC
    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.

      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 (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
Re: Problems with recent PM update and Safari
by adrianh (Chancellor) on Oct 03, 2003 at 21:21 UTC

    I've just switched to red theme, no custom CSS... lets see if we get a crash...

    Nope. Worked fine. On Mac OS X 10.2.8, Safari 1.0 (v85.5).

Re: Problems with recent PM update and Safari
by bradcathey (Prior) on Oct 04, 2003 at 01:45 UTC
    I'm trying it now (10.2.6)
      No problems, but do notice that I don't get a flashing cursor in the text box. Anyway, back to the altar of Bill Gates and IE (not real happy with the way Safari renders certain sites).
Re: Problems with recent PM update and Safari
by naChoZ (Curate) on Oct 06, 2003 at 13:47 UTC

    Did this start at about the same time that the code for wrapping div tags around sigs was added? Do you have anything in your style sheet that might bork it?

    Also, I recently got to play with OSX (10.2.6 iirc) for a few days. I installed Opera on it and it seemed to work pretty flawlessly. You'll have to use Opera 6 because they haven't released Opera 7 for that platform yet, but it'll be worth the wait. Opera 6 is still very functional. Just lacks some of the customizable features in 7.

    "I just read perlman:perlboot," said Tom, objectively.

(wil) Re: Problems with recent PM update and Safari
by wil (Priest) on Oct 13, 2003 at 09:32 UTC
    Since upgrading to 10.2.8 (twice - thanks Apple), this problem seems to have solved itself. I've now created a handful of replies and Safari hasn't crashed on me yet. What version of OS X are you running? Have you made the latest (free) upgrade?

    - wil

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: monkdiscuss [id://296391]
Approved by BazB
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (4)
As of 2024-04-16 10:51 GMT
Find Nodes?
    Voting Booth?

    No recent polls found