Ruby on Rails | Screencasts | Download | Documentation | Weblog | Community | Source

Ticket #2310 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Sortable Lists crashing Safari v. 2.0.1 (412.5)

Reported by: beckleyworks@verizon.net Assigned to: thomas@fesch.at
Priority: normal Milestone:
Component: script.aculo.us Version: 0.13.1
Severity: normal Keywords:
Cc:

Description

The Sortable Lists demo quits Safari v. 2.0.1 (Exception: EXC_BAD_ACCESS (0x0001), Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000) in Mac OS X 10.4.2. I implemented a demo in a site using the latest code & get the same result. Happened on multiple machines.

Change History

09/26/05 14:59:15 changed by madrobby

Can you please provide a working test case of this?

I'm doing all my development with Firefox and Safari, and I have no crashes here.

09/26/05 15:00:21 changed by madrobby

Sorry, I should read the ticket before answering. :)

09/26/05 15:03:44 changed by beckleyworks@verizon.net

also found this in the logs:

[3776] http://weed.rbse.com/javascripts/weed.js:TypeError - Value undefined (result of expression Weed.Tests[test].run) is not object. [3776] http://wiki.script.aculo.us/scriptaculous/show/GhostlySortableDemo:SyntaxError - Parse error [3776] http://weed.rbse.com/javascripts/extra.js:ReferenceError - Can't find variable: Element

09/26/05 15:16:58 changed by madrobby

Thanks for reporting! It seems I've already found the problem. Draggables register- and unregister their events when in use/not used, this seems to cause Safari to crash (of course it shouldn't, but it does).

I'm reverting the implementation to just register the events once. This _should_ solve the problem. I'll commit the new version shortly.

09/26/05 15:24:35 changed by madrobby

Please see changeset [2344].

I updated the scripts on the wiki site to use this version, so please test there again (be sure to reload the pages completly!).

09/29/05 03:47:02 changed by madrobby

  • status changed from new to closed.
  • resolution set to fixed.

As I'm not getting any negative reports on this, I'm assuming this was indeed fixed with changeset [2344].

Feel free to reopen this ticket if you still have problems.