Welcome to WebmasterWorld Guest from 54.234.38.8

Forum Moderators: open

Message Too Old, No Replies

out of memory line 2 by ajax or?

out of memory

     
12:02 am on Mar 25, 2007 (gmt 0)

Junior Member

10+ Year Member

joined:Jan 3, 2005
posts:187
votes: 0


Hello,
Im a bit unsure if this is the right forum..

but here's me question..
after updating a component for my website in IE 7 you get :

"out of memory line 2"

Line 2 = <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

So nothing special..

in firefox everything is ok..

but also when i install it on another site all is ok with that new version..
and that makes it even weirder i guess..

Yes the stuff uses ajax and javascript and looks like :

<script type='text/javascript'> /*<![CDATA[*/ var jc_option = "com_frontpage"; var jc_autoUpdate = "0"; var jc_update_period = 300*1000; var jc_orderBy = "1"; var jc_commentForm; var jc_livesite_busyImg = "http://www.example.com/pcajaxcomment/busy.gif"; /*]]>*/ </script>
<script src="http://www.example.com/pcajaxcomment/script.js?1.7" type="text/javascript"></script>

<script type='text/javascript'>
/*<![CDATA[*/
var jax_live_site = 'http://www.example.com/index.php';
/*]]>*/
</script>

does this sounds familiar to someone?
or anyone have a clue where the error suddenly comes from?

Thank you

[edited by: encyclo at 4:57 pm (utc) on Mar. 29, 2007]
[edit reason] switched to example.com [/edit]

4:34 pm on Mar 29, 2007 (gmt 0)

Full Member

5+ Year Member

joined:Feb 12, 2006
posts:224
votes: 0


Line 2=<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

I thought the doctype was meant to be line 1.
6:29 pm on Mar 29, 2007 (gmt 0)

Senior Member

WebmasterWorld Senior Member penders is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:July 3, 2006
posts: 3123
votes: 0


"out of memory line 2"

The line number that IE reports as the location of the error may not be in the (HTML) source file that it reports... it may be (and probably is) a line in an external JS file (script.js perhaps).

But I imagine the line# reported in an 'out of memory' error is unlikely to be the pin-pointed source of the problem, more like the point at which the script ran out of memory....?!

 

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members