Bug 99779

Summary: Safari crashes after viewing twit.tv for a while
Product: WebKit Reporter: Paul Riley <paul2590>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://www.twit.tv
Attachments:
Description Flags
this is a screen shot of my installation... none

Paul Riley
Reported 2012-10-18 17:36:54 PDT
I purchased RAMDrive in the APP store for five dollars and that is the location of the webkit browser. I didn't try on this release on the morning of October 18 yet but about twenty minutes into show the web browser quits unexpectedly. This also happens with Safari browser from Apple. I simply re-launch the browser and resume the show when this happens. It has been at least a few months that Safari has been like this and was surprised when webkit also behaved like this.... There is over one gigabyte free on RAMDrive with webkit installed.
Attachments
this is a screen shot of my installation... (1.05 MB, image/png)
2012-10-18 17:40 PDT, Paul Riley 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Paul Riley
Comment 1 2012-10-18 17:40:25 PDT
Created attachment 169514 [details] this is a screen shot of my installation... maybe this behavior in browser is because of the way it is installed on my computer in the RAMDrive.....
WebKit Review Bot
Comment 2 2012-10-18 17:42:55 PDT
Attachment 169514 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files']" exit_code: 1 Total errors found: 0 in 0 files If any of these errors are false positives, please file a bug against check-webkit-style.
Alexey Proskuryakov
Comment 3 2012-10-19 14:41:42 PDT
FWIW, I had this stream open in Safari 6.0.1 for two hours, and didn't hit any issues.
Darin Adler
Comment 4 2013-01-21 16:36:31 PST
Comment on attachment 169514 [details] this is a screen shot of my installation... The review and commit-queue flags are for patches, not screenshots.
Note You need to log in before you can comment on or make changes to this bug.