Biolab Disaster

Out of context: Reply #20

• Started
• Last post
• 62 Responses

• Boz0

  well it's crap.. nothing to be sore about..

  plus it crashes safari like motherf***er.

  "Process: Safari [1238]
  Path: /Applications/Safari.app/Content...
  Identifier: com.apple.Safari
  Version: 5.0.2 (6533.18.5)
  Build Info: WebBrowser-75331805~1
  Code Type: X86-64 (Native)
  Parent Process: launchd [105]

  Date/Time: 2010-09-13 17:12:05.471 -0700
  OS Version: Mac OS X 10.6.4 (10F569)
  Report Version: 6

  Interval Since Last Report: 188720 sec
  Crashes Since Last Report: 2
  Per-App Interval Since Last Report: 250109 sec
  Per-App Crashes Since Last Report: 1
  Anonymous UUID: 8BC8CBAE-48F2-4291-A8C4-C8E1BDC8...

  Exception Type: EXC_BAD_ACCESS (SIGSEGV)
  Exception Codes: 0x000000000000000d, 0x0000000000000000
  Crashed Thread: 9"

  LOL.. just proves that when you have shit ton of code and running it in javascript/canvas you will crash a browser much easier than Flash player does, completely negating talking points against Flash.

  Boz 0Permalink

  UpvoteDownvote

  Flag

  • cool story braernexbcn
  • proves you have a bad ram module, actuallymonospaced
  • EXC_BAD_ACCESS is what crashed your browser. It has NOTHING to do with the code. RAMmonospaced
  • bad ram, broduckofrubber
  • works fine on my Safari...Amicus

  Show [[ numHiddenNotes ]] more notesAdd Note

  SaveCancel

View thread