Bug 17215 - Select list and "ajax" makes Safari beta for win to crash
Summary: Select list and "ajax" makes Safari beta for win to crash
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 523.x (Safari 3)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-08 03:19 PST by ashish
Modified: 2008-02-27 21:43 PST (History)
1 user (show)

See Also:


Attachments
safari crash log (29.67 KB, application/octet-stream)
2008-02-08 03:20 PST, ashish
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description ashish 2008-02-08 03:19:08 PST
+++ This bug was initially created as a clone of Bug #14950 +++

I am also facing the same problem with Safari on winXP. My AJAX code is running only once and the 2nd time it just crashes the Safari browser.

I have user.dmp file with me, can you please suggest where to upload this file?

Ashish
Comment 1 ashish 2008-02-08 03:20:05 PST
Created attachment 19002 [details]
safari crash log
Comment 2 Adam Roben (:aroben) 2008-02-08 08:04:47 PST
Ashish, have you tried your page with a WebKit nightly build? Nightly builds can be downloaded from <http://nightly.webkit.org/>. Bug 14950 was closed because the issue seemed to be fixed with a nightly build. Please try and let us know what happens.
Comment 3 ashish 2008-02-16 00:11:57 PST
I have downloaded the WebKit but I could not configure that. What are
the steps I have to perform after downloading the toolkit can you
please send any ref link. I am using safari on windowsXP.

Ashish Sharma(In reply to comment #2)
> Ashish, have you tried your page with a WebKit nightly build? Nightly builds
> can be downloaded from <http://nightly.webkit.org/>. Bug 14950 was closed
> because the issue seemed to be fixed with a nightly build. Please try and let
> us know what happens.
> 

Comment 4 Matt Lilek 2008-02-16 08:40:33 PST
(In reply to comment #3)
> I have downloaded the WebKit but I could not configure that. What are
> the steps I have to perform after downloading the toolkit can you
> please send any ref link. I am using safari on windowsXP.
> 
> Ashish Sharma(In reply to comment #2)
> > Ashish, have you tried your page with a WebKit nightly build? Nightly builds
> > can be downloaded from <http://nightly.webkit.org/>. Bug 14950 was closed
> > because the issue seemed to be fixed with a nightly build. Please try and let
> > us know what happens.
> > 
> 

Once you've downloaded the zip archive from the nightly site, just right click it and select "Extract All".  Once unzipped, open the folder it created and double click the "run-webkit-nightly" icon.  Make sure Safari is closed before you run that script, otherwise the newer WebKit included with it will not be loaded.
Comment 5 ashish 2008-02-27 21:43:16 PST
(In reply to comment #4)

I have downloaded the webkit and perform the action as you have mentioned in your mail. But the problem is still there. I am using jquery's ajax function. But i don't think it is jquery's problem. It is working fine on Firefox and IE. I have not found any kind of error in Firefox's firebug and IE's debugger and memory leack tracker.

Ashish 

> (In reply to comment #3)
> > I have downloaded the WebKit but I could not configure that. What are
> > the steps I have to perform after downloading the toolkit can you
> > please send any ref link. I am using safari on windowsXP.
> > 
> > Ashish Sharma(In reply to comment #2)
> > > Ashish, have you tried your page with a WebKit nightly build? Nightly builds
> > > can be downloaded from <http://nightly.webkit.org/>. Bug 14950 was closed
> > > because the issue seemed to be fixed with a nightly build. Please try and let
> > > us know what happens.
> > > 
> > 
> 
> Once you've downloaded the zip archive from the nightly site, just right click
> it and select "Extract All".  Once unzipped, open the folder it created and
> double click the "run-webkit-nightly" icon.  Make sure Safari is closed before
> you run that script, otherwise the newer WebKit included with it will not be
> loaded.
>