[macvoiceover] Re: adium extras

  • From: Jacob Schmude <j.schmude@xxxxxxxxx>
  • To: macvoiceover@xxxxxxxxxxxxx
  • Date: Sun, 14 Jun 2009 16:04:06 -0400

Ouch, confirmed on my Macbook, Safari 4.0/OS X 10.5.7. Looking at the trace, it appears to be a memory protection error, i.e. the Webkit rendering engine is trying to use a portion of memory that it does not have permission to manipulate, and it seems to be triggered by a javascript while the page is loading, but I'm not sure which script specifically in conjunction with Voiceover is causing this condition. This seems to be fixed in the latest Webkit build, as I do not get a crash there, but this is something we need to get on Apple's case about. This also happens on the Apple store, at least for me and probably for others. This is most definitely a regression, as nothing like this was happening in the beta. I guess I have a reason to have to use Webkit again. *sigh*. Come on Apple, a bit more testing in the future would be appreciated... first the iTunes 8.1 issues, now this? Make sure to write to accessibility@xxxxxxxxx describing this bug as well. The more people testing and reporting it, the sooner it'll get fixed. I'm also going to write and express my serious concerns over some accessibility-related regressions of late. In the meantime you can either use the latest Webkit build (see www.webkit.org to download that) or unload voiceover before visiting a page that crashes and reloading it. This issue only seems to happen while the page is loading, not once it's loaded, so whichever script is doing this is running at load time. In short, this has already been fixed, but either it was fixed after Safari 4 was released or the patch did not make it into the final release. Either way, it's nasty and needs to be included. Let's bug Apple everyone.



On Jun 14, 2009, at 14:30, Chris G wrote:

Hello,

I updated to the latest safari and when i try and browse the adium
extras  page safari crashes.

I don't know if it worked in the previous version as I only discovered adium after
I updated the web browser.

Is anyone  else seeing  the crash?
I sent the error report to Apple.

Chris

--
The home of the Mystic Place blog and podcast.
www.mysticplace.info
RSS: feeds.feedburner.com/mysticplacebp


Click on the link below to go to our homepage.
http://www.icanworkthisthing.com

Manage your subscription by using the web interface on the link below.
//www.freelists.org/list/macvoiceover

Users can subscribe to this list by sending email to
macvoiceover-request@xxxxxxxxxxxxx
with 'subscribe' in the Subject field OR by logging into the Web
interface at //www.freelists.org/list/macvoiceover


The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.
        --Douglas Adams


Click on the link below to go to our homepage.
http://www.icanworkthisthing.com

Manage your subscription by using the web interface on the link below.
//www.freelists.org/list/macvoiceover

Users can subscribe to this list by sending email to macvoiceover-request@xxxxxxxxxxxxx with 'subscribe' in the Subject field OR by logging into the Web interface at //www.freelists.org/list/macvoiceover

Other related posts: