or Connect
AVS › AVS Forum › AVS Forum Information › Forum Operations Center › Viewing last page of threads (& composing posts) causes Safari 7.0 to quit the page unexpectedly (and reload) at short intervals
New Posts  All Forums:Forum Nav:

Viewing last page of threads (& composing posts) causes Safari 7.0 to quit the page unexpectedly...

post #1 of 37
Thread Starter 
I'm running OS X v10.9 on a MacBook Pro and using Safari v7.0 (9537.71).

Here is a screen shot of the behaviour. This happens every 3 to 5 minutes when using the editor including after a preview pane has been opened.


This behaviour only started about two days ago and I suspect it may have coincided with the new(?) draft auto save feature on the post editor (that's the first time I noticed the feature anyway). It happens whether I'm quoting another post or not.

This must be only when replying to existing threads - it hasn't happened composing and previewing this OP. I also cannot see the draft saving feature at the base of this editor.

Any suggestions? Can you investigate and if possible rectify at your end? I can attach the report file that Safari generates if that will help.
post #2 of 37

Is it this?

 

https://discussions.apple.com/search.jspa?q=%22JavaScriptCore%3A%3AMarking%22

 

If so, it seems to be an issue w/ Safari 7 causing issues w/ lots of sites.

post #3 of 37
This Safari browser crash is also happening with Safari 6.1 on Mac OS X 10.8.5.

It is the JavaScript "Marking" thread which is crashing.

THE WORKAROUND FOR NOW IS TO TEMPORARILY TURN OFF JAVASCRIPT -- AT LEAST WHILE CREATING A POST. Do this in Menu Bar > Safari > Preferences > Security > Web Content.

With JavaScript disabled you will avoid the crashing behavior, but you will lose some automated functionality of the forum. For example you will have to go to the page of Forums to select a new Forum instead of using the pull-down menu. And you won't have access to formatting features like "Bold" when writing a post.



Mike, it appears the crash is triggered by the automated Save a Draft functionality, which I think may be a recent addition.

Is there a way for a user to disable automated Save a Draft to check this?
--Bob
post #4 of 37
Thread Starter 
Quote:
Originally Posted by Mike Lang View Post

Is it this?

https://discussions.apple.com/search.jspa?q=%22JavaScriptCore%3A%3AMarking%22

If so, it seems to be an issue w/ Safari 7 causing issues w/ lots of sites.

Yes Mike, that appears to be it. As Bob indicates, I'm now certain that the crashing is triggered by the draft saving functionality because I had no instances of this prior to about 3 days ago and no problems creating the OP of this thread.

Quote:
Originally Posted by Bob Pariseau View Post

This Safari browser crash is also happening with Safari 6.1 on Mac OS X 10.8.5.

It is the JavaScript "Marking" thread which is crashing.

THE WORKAROUND FOR NOW IS TO TEMPORARILY TURN OFF JAVASCRIPT -- AT LEAST WHILE CREATING A POST. Do this in Menu Bar > Safari > Preferences > Security > Web Content.

With JavaScript disabled you will avoid the crashing behavior, but you will lose some automated functionality of the forum. For example you will have to go to the page of Forums to select a new Forum instead of using the pull-down menu. And you won't have access to formatting features like "Bold" when writing a post.



Mike, it appears the crash is triggered by the automated Save a Draft functionality, which I think may be a recent addition.

Is there a way for a user to disable automated Save a Draft to check this?
--Bob

Thanks very much for the explanation and the tip Bob! I too would like to know if there's a way of disabling automated Save a Draft.
post #5 of 37

There were more than two dozen changes in the last update, the draft saving is just the most visible to end users. There may be others that also involved changes with javascript.

 

From what I've read, this was a preexisting issue w/ Safari that the update exacerbated. Our programmers are also trying to narrow it down. I've read that Safari 7.0.1 fixes it.

 

There's no way to disable daft saving, it works on both editors and even mobile. Obviously, killing off javascript, or using Firefox or Chrome is the temporary workaround.

 

I'll update here if I get any more info.

post #6 of 37
^ Mike, I just saw a post from one of the other OPPO Beta Testers that AVS posting is now crashing on his iPad as well. I haven't been able to nail it down definitively, but it does seem that the timing of the crash using Safari 6.1 is consistent with when the auto Save a Draft kicks in and tries to do its thing.

To test it, type in a few words of a new reply post and then just wait -- doing nothing -- looking for the Discard Draft button to show up indicating that a Save a Draft has happened.
--Bob
post #7 of 37
I'm on an ipad right now and have been using both an ipad and iphone all along. I haven't seen any issues with them at all. I watched it save several times between pauses on this post.
post #8 of 37
I have 2 macs one with safari 7 and one with safari 6.1. In both cases crashes started a few days ago and have rendered safari completely unusable with avs (I'm typing this on firefox 21 which has no problem whatsoever). Indeed it seems related to the draft save as mentioned above by Bob Pariseau. The mobile version of safari works just fine for me though - I've made several replies on my iphone without any issue (iOS 7.0.4)
post #9 of 37
FWIW the "draft save" function is pretty useless even when it does work right, and causes more work than it saves.
post #10 of 37
Glad I'm not the only one getting this. FYI, I'm still on OS X 10.8.5 w/Safari 6.1. Thanks for the tip about disabling JavaScript. I'm going to try that now, though I suspect that will cause me too much pain when viewing other sites. It doesn't look like I can disable it for just one website. I had been holding off on upgrading to Mavericks because I knew that my Parallels 7 / Windows 7 would break, but I just scored a deal on a cheap copy of Parallels 8, so that will be a non-issue soon enough. I'm guessing that another option could be to use Firefox or Chrome, no?
post #11 of 37

 

 

Quote:
Originally Posted by Mike Lang View Post
Obviously, killing off javascript, or using Firefox or Chrome is the temporary workaround.

 

 

Quote:

Originally Posted by srauly View Post
I'm guessing that another option could be to use Firefox or Chrome, no?

 

:cool:

post #12 of 37
Sorry, I overlooked that last post of yours.
post #13 of 37
Quote:
Originally Posted by srauly View Post

Glad I'm not the only one getting this. FYI, I'm still on OS X 10.8.5 w/Safari 6.1. Thanks for the tip about disabling JavaScript. I'm going to try that now, though I suspect that will cause me too much pain when viewing other sites. It doesn't look like I can disable it for just one website. I had been holding off on upgrading to Mavericks because I knew that my Parallels 7 / Windows 7 would break, but I just scored a deal on a cheap copy of Parallels 8, so that will be a non-issue soon enough. I'm guessing that another option could be to use Firefox or Chrome, no?

In Safari 6.1 (probably the same in 7.0, but I haven't tried it) you can leave the small, Safari Preferences window on screen all the time while on AVS. When browsing and reading you can leave JavaScript enabled. When you want to type in a new Post or Reply, clear the check box in Preferences to disable JavaScript before going to the text type-in window in AVS. When you are done Submitting your new Post or Reply, click the check box again to re-enable JavaScript.

A nuisance to be sure, but better than leaving JavaScript turned off all the time.
--Bob
post #14 of 37
I'm having this problem also (just started for me here today, but I don't remember the last time I was on here). The same thing is happening at appleinsider.com, which I suspect is using the same forum software (although their UI is far worse than yours). Didn't happen there before a week ago either.

There have been no recent software updates on my Mac. I'm running OSX 10.8.5 and Safari 6.1.

Assuming that you're using the same Forum software as appleinsider, this would seem to be a Forum software issue, not a Safari bug, as it never happened before the last few days on either site. If you're not using the same tool as they are, then I would concede that something else is at play here.

I'm writing this with JavaScript disabled and it seems to work.
post #15 of 37
Apple just pushed out Safari 6.1.1 for Mac OS X 10.8.5 users.

So far, it seems to fix this problem. I.e., I can now type in Posts reliably without having to turn off JavaScript first.

Apple also just pushed out Mac OS X 10.9.1 for Mavericks (10.9) users which includes Safari 7.0.1. It wouldn't surprise me if that fixes this problem for Safari 7.0 users as well.
--Bob
post #16 of 37

Good to read!

post #17 of 37
Testing safari 6.1.1 as I type this. Indeed, the problem has been fixed. cool.gif

I'll add that version 6.1.1 is not just for Mountain Lion (10.8.x) but for Lion as well (10.7.x).


I can now put firefox back where it belongs! wink.gif
post #18 of 37
Quote:
Originally Posted by Mike Lang View Post

There were more than two dozen changes in the last update, the draft saving is just the most visible to end users. There may be others that also involved changes with javascript.

From what I've read, this was a preexisting issue w/ Safari that the update exacerbated. Our programmers are also trying to narrow it down. I've read that Safari 7.0.1 fixes it.

There's no way to disable daft saving, it works on both editors and even mobile. Obviously, killing off javascript, or using Firefox or Chrome is the temporary workaround.

I'll update here if I get any more info.

Little more testing next time? smile.gif

I vote to get rid of the auto save feature as well...PITA - at least make it a clickable button "Save Draft" that a user can press/click when they want to.
post #19 of 37
Quote:
Originally Posted by thrang View Post
 
Quote:
Originally Posted by Mike Lang View Post

There were more than two dozen changes in the last update, the draft saving is just the most visible to end users. There may be others that also involved changes with javascript.

From what I've read, this was a preexisting issue w/ Safari that the update exacerbated. Our programmers are also trying to narrow it down. I've read that Safari 7.0.1 fixes it.

There's no way to disable daft saving, it works on both editors and even mobile. Obviously, killing off javascript, or using Firefox or Chrome is the temporary workaround.

I'll update here if I get any more info.

Little more testing next time? smile.gif

I vote to get rid of the auto save feature as well...PITA - at least make it a clickable button "Save Draft" that a user can press/click when they want to.


+1(to getting rid of auto save, never had issues with AVS until it was enabled)

post #20 of 37
Posting on this forum now raises my blood pressure by 20 points -- this needs to be fixed ASAP!
post #21 of 37
Trying to post causes CPU to peg before it crashes.

Now posting from iPad 3 on iOS 7.0.4 and the typing is CRAWLING!.

Can the forum software be reverted?
post #22 of 37
Thread Starter 
I note that the auto draft saving function has now been removed. Problems with Safari (7.0) crashing have ceased.

Merry Christmas to all at AVS! smile.gif
post #23 of 37
Quote:
Originally Posted by Deja Vu View Post

Posting on this forum now raises my blood pressure by 20 points -- this needs to be fixed ASAP!


Oh come on now! is a problem with a browser that has less than 10% market share really enough to raise your blood pressure?

post #24 of 37
Quote:
Originally Posted by GIEGAR View Post

I note that the auto draft saving function has now been removed. Problems with Safari (7.0) crashing have ceased.

Merry Christmas to all at AVS! smile.gif


It was better for a few days, now it's back worse than before! Has the "auto save" function been turned back on? Got bad again last night and this morning is no better!

post #25 of 37
Quote:
Originally Posted by jjeff View Post


Has the "auto save" function been turned back on?

No, it's still off and this thread is about the issues before Safari released their fix. You said you're a Windows/Firefox user. confused.gif
post #26 of 37
Thread Starter 
Quoting myself for context:
Quote:
Originally Posted by GIEGAR View Post

I note that the auto draft saving function has now been removed. Problems with Safari (7.0) crashing have ceased.

Merry Christmas to all at AVS! smile.gif

As of about 5 days (?) ago, the problem has re-emerged and is actually worse in scope. In addition to crashing while composing posts, Safari 7.0 now continually crashes (and reloads) when simply viewing the last page page of a thread. (That is, It does not occur when viewing index pages or thread pages other than the last page.) The onset of this behaviour appeared to coincide the introduction of new blue navigation tabs at the bottom of the page, however I've only spotted these a couple of times. As before, disabling JavaScript is the workaround, but this is a real annoyance.

I will attempt to edit the thread title to reflect the broader scope of the problem.

I trust that action can be taken to again rectify this issue.
post #27 of 37
Yes, I agree, trying to use the forum from an iPad is a challenge. Safari crashes about every 30-60 seconds. What the heck is happening? Please make it stop.
post #28 of 37
Testing from iPad...
post #29 of 37
Quote:
Originally Posted by GIEGAR View Post

 The onset of this behaviour appeared to coincide the introduction of new blue navigation tabs at the bottom of the page, however I've only spotted these a couple of times.

 

You can disable the alert bar if it's causing you issues.

post #30 of 37
Quote:
Originally Posted by Mike Lang View Post

You can disable the alert bar if it's causing you issues.

OK, I did that. Let's see if it makes a difference. Just curious, I don't recall having this many issue with the iPad several months ago. Are the current problems associated with the latest iOS upgrade?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Forum Operations Center
AVS › AVS Forum › AVS Forum Information › Forum Operations Center › Viewing last page of threads (& composing posts) causes Safari 7.0 to quit the page unexpectedly (and reload) at short intervals