Open Bug 593581 Opened 15 years ago Updated 3 years ago

Unable to log into lordofultima.com browser game

Categories

(Core :: XUL, defect)

x86
Windows Vista
defect

Tracking

()

UNCONFIRMED

People

(Reporter: hAbI_rAbI, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:2.0b6pre) Gecko/20100904 Firefox/4.0b6pre Build Identifier: Mozilla/5.0 (Windows NT 6.0; rv:2.0b6pre) Gecko/20100904 Firefox/4.0b6pre Since the 20100825 build I've been unable to log into the Lord of Ultima online game. I always get an error which can be reported to the devs of the game. Oddly enough it works fine with the 20100824 build. Whenever I try to log in I get an error in the Error Console like the one shown below. Error: uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDOMHTMLDocument.createElementNS]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: http://prodgame04.lordofultima.com/6/294884/script/webfrontend.js :: anonymous :: line 9257" data: no] Not sure if this is a problem that is on Firefox' side or the game's side but I thought I'd better report it. Reproducible: Always
Version: unspecified → Trunk
Could you bisect this on the nightly builds to find the exact day it stopped working?
20100824 works 20100825 and later don't work Or do you want me to check the hourlies?
(In reply to comment #2) > 20100824 works > > 20100825 and later don't work Whoops, I didn't see that you already gave a 24-hour window. Thanks. Based on that, the changeset regression range looks like it is: good: http://hg.mozilla.org/mozilla-central/rev/9a623cc1c5e7 bad: http://hg.mozilla.org/mozilla-central/rev/d6ea766463f0 It looks like it is not necessarily a JS bug, but someone would have to pinpoint the regressing change in order to figure that out. > Or do you want me to check the hourlies? I didn't even know we had hourly builds. But if you can give a tighter regression range, by all means, please do.
I might have something more interesting than that. I just tried confirming the regression happened between those nightlies I mentioned. I can confirm that 20100824 works fine. With 20100825 I am getting the following crashes. I'm just posting one of the reports since they all look the same. http://crash-stats.mozilla.com/report/index/b2a4c8f5-ee6b-462d-9bbf-0622e2100907 Is it possible that the login uses remote XUL and that's what's causing the error?
(In reply to comment #4) > I might have something more interesting than that. I just tried confirming the > regression happened between those nightlies I mentioned. > > I can confirm that 20100824 works fine. With 20100825 I am getting the > following crashes. I'm just posting one of the reports since they all look the > same. > > http://crash-stats.mozilla.com/report/index/b2a4c8f5-ee6b-462d-9bbf-0622e2100907 > > Is it possible that the login uses remote XUL and that's what's causing the > error? Good work. You're talking about bug 546857, right? That did land in that range. Sending over to XUL.
Assignee: general → nobody
Component: JavaScript Engine → XUL
QA Contact: general → xptoolkit.widgets
The crash references Bug 590858 and Bug 590858. But those are both caused by Bug 546857 so yea this issue could be caused by Bug 546857. Unfortunately I don't know how to confirm that. I'm just deducing it from the crash.
I suspect you're referencing the wrong bug somewhere in the previous message since you reference the same bug number twice... Anyhow, bug 590870 is the crash you are seeing. It was fixed a few days after XUL was disabled and so in beta 5 you should only see the exception mentioned in comment 0. It does indeed appear as if Lord of Ultima is using XUL which we no longer allow web pages to do. Does anyone have contact information with the developers there so that we can get them to fix their site?
I posted on their bug report forum but they don't reply to those apparently. I'm guessing this the following page, and maybe their Twitter and Facebook accounts are ways to contact them. Since I don't use Facebook and only have a private Twitter account I can't use those ways of communication. Maybe you guys would like to contact them directly. http://www.lordofultima.com/en/help/inquire Btw Comment 4 and Comment 6 are both related to me testing with the nightly build 20100825 which didn't have the crash fix. The first two crash references in Comment 6 are the same because I messed up copy and pasting the bug number.
Hi and thanks for making us aware of this problem! We'll start working on a fix for this as soon as possible. /Developers
For the record, the team was apparently already aware but it was news to me. :)
While we got your attention might I also point you to the bug 576726? I am guessing that dbaron and vlad would appreciate any way you could help them fix that memory issue.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.