Side navigation
#2766 closed bug (invalid)
Opened April 30, 2008 06:53PM UTC
Closed February 14, 2009 05:22PM UTC
Firefox 3: Out of Memory
Reported by: | docwhat | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.3.2 |
Component: | core | Version: | 1.3.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
This is with Firefox 3 Beta 5 on Mac OS X 10.5.2
I get the following error:
out of memory
http://docwhat/wp-includes/js/jquery/jquery.js?ver=1.2.3
Line 629
This is in the WordPress 2.5.1 product with an uncompressed pristine jquery.js (v 1.2.3) so that the line numbers are useful.
Here is the code in question:
627 isFunction: function( fn ) { 628 return !!fn && typeof fn != "string" && !fn.nodeName && 629 fn.constructor != Array && /function/i.test( fn + "" ); 630 },
Ciao!
Attachments (0)
Change History (7)
Changed April 30, 2008 06:54PM UTC by comment:1
Changed April 30, 2008 07:00PM UTC by comment:2
It occurs to me that this may be something unique on my website. If so, you can see the error just visiting the site (I use jquery on the front page): http://docwhat.gerf.org/ If someone needs me to replace the packed (default) jquery with an expanded one, I can do that.
Ciao!
Changed May 07, 2008 02:16AM UTC by comment:3
I've got the same issue with FF3 B5 on Ubuntu Hardy.
Changed May 11, 2008 10:16PM UTC by comment:4
Could you post a link ?
Changed May 12, 2008 01:52AM UTC by comment:5
http://docwhat.gerf.org/ causes this problem. I can see about making a version with the file uncompressed to show you where the line number ends up.
Ciao!
PS: Firebug is also looking at this issue: http://code.google.com/p/fbug/issues/detail?id=653
Changed July 11, 2008 08:15PM UTC by comment:6
I get this error too (same line) on a different page (not public) in FF3 release. It only happens when the Firebug extension is installed.
Changed February 14, 2009 05:22PM UTC by comment:7
milestone: | 1.2.4 → 1.3.2 |
---|---|
resolution: | → invalid |
status: | new → closed |
version: | 1.2.3 → 1.3.1 |
This appears to be an issue with Firebug.
Under Linux & Mac Os X with Version 2.0.0.14 Firefox reports this error instead: