Home » Downloads » Issues

Browser Crashes when using iframes

Submitted by msalamon on Wed, 2007-03-28 15:49.
Project:formsPlayer
Version:1.5.1
Component:Code
Category:bug
Priority:normal
Assigned:Unassigned
Status:postponed
Description

I have been having this problem for a few weeks. I just upgraded to the newest version (1024) and still have the same problem.

The problem occurs when I submit an xform. All of my xforms are embedded in an html page using the iframe element, so there are addtl html elements "outside" of the xforms iframe. If th submission is successful, my xform invokes the following action:

although the resource is different based on the type of submission, in all cases what ends up happening is that another page gets loaded that contains an xform embedded in an iframe. I can see that the new page is loading successfully, b/c the html outside of the xform is displayed (and the jsp code that is on that page also run on the server side). But as the xform attempts to load, I get this IE error:

"Internet Explorer has encountered a problem with an add-on and needs to close. The following add-on was running when this problem occurred. File: formsPlayer.dll..." When I hit continue, i get this addtl error message: "The instruction at "0x055bf1ba" referenced memory at "0x00000020". The memory could not be "written".

This happens 50% of the time on the first xforms:load that occurs after I restart the browser, and 50% of the time on the 2nd time an xforms:load is reached.

Btw, I have run into this problem on different computers. I am using IE 6.0.29x.

It almosts seems as though something about xforms remains cached in the browser and then causes a conflict or memory problem when another xforms is attempted to be loaded.

Updates

#1 submitted by Paul Butcher on Wed, 2007-03-28 17:48

Is it possible for you to provide us with a link or sample form that demonstrates this issue? Does it still occur in version 1.5.1.1026?

#2 submitted by msalamon on Mon, 2007-04-09 15:11

It still happens with 1029, which I just installed. Let me see about getting you more details on the other stuff.

#3 submitted by msalamon on Thu, 2007-04-19 21:57
Attachment:fp.zip (10.55 KB)

I have attached three files to help debug this (all zipped up).

the way I have my xform set up is inside an iframe in an html/jsp/jsf page.

i have attached:
(1) the rendered html page
(2) the xform inside the iframe
(3) the jsp page

If you look in the xform, you will see this line:

<xforms:load resource="http://pcny1205-a.f112.xxx.com:8080/due_diligence/jsp/project/create-form.faces?category=employment_agreement" show="replace" ></xforms:load>

basically, when you successfully submit a page, it reloads the same page (create-form.jsp, or create-form.faces b/c I'm sort of using jsf). b/c this is being called inside an iframe (and the xforms:load does not have a target attribute, so I can't do target="_top"), inside the jsp page I have this code:

When I submit a form and the page reloads, usually I get a crash b/f the new page tries to load the next time. but sometimes i get 5 or 6 submissions before this happens. The crashing also happens in another similar context, but I think this should be enough information. i have seen this behavior on lots of different computers using an updated version of IE6. (I have not tried IE7, as our company has not upgraded to that yet.)

#4 submitted by Mark Birbeck on Thu, 2007-04-19 23:34

I don't see any reference to xf:load in the form. Have you sent the correct forms? Also, there's no point in sending a JSP--far better to take a snapshot of the form that the JSP generates, and send that. Then we can reproduce this without having to set servers up.

#5 submitted by msalamon on Fri, 2007-04-20 19:41

I managed to resolve (not solve) this issue by putting the content inside a instead of inside an iframe. This also allowed me to get rid of the js that detected whether the window was on top when xforms:load is called, b/c all of the content is in the same window. so the issue with iframes, et al. is still out there, but using div's seems like a workable alternative.

#6 submitted by Mark Birbeck on Tue, 2007-06-12 12:52
Title:Browser Crashes» Browser Crashes when using iframes
Priority:critical» normal
Status:new» postponed

Postponing this for now and removing 'critical' priority.

»