1 Nov
2006
1 Nov
'06
5:04 p.m.
In a sane world, this would serve as just one more reason not to click
on the blue 'e'. In my world, however, it threatens to scuttle a
project to re-host an enterprise-wide reference web site, so I'm hoping
someone else has seen this. Considering how little I have to go on, I'm
embarassed to share it with the list, but I'm approaching desparation.
The evidence I have is sketchy, so the characterization is a bit thin,
but here goes:
On XWiki 0.9.840, IE occasionally crashes while reloading a document
after saving it. The save succeeds, and reloading the doc again causes
no problems. I don't yet have a handle on the browser's memory use or
anything characterizing the other docs the users have visited, but it
appears to be unrelated to the specific document. At the moment I'm not
aware of crashes at any other times, so I'm grateful for that much,
being the firmest bit of evidence I've got.
Anyone had any similar experiences that might shed light on the subject?
brain[sic]
1 Nov
1 Nov
5:37 p.m.
New subject: [xwiki-users] IE browser crash
IE can be a real nasty piece of work when it's not treated right, and
often even when it is.
I usually use firefox and the 3rd party extension called "Web Developer"
as this provides a page tester which tests even CSS errors (among other
very useful tools for general web development)
However, as you're talking IE, I still have some suggestions for you to
start out with.
[note: the following may sound patronising and are fairly low grade
checks, easy to do and quick to rule out common issues]
First things first though, if you are using IE7 then I would first test
with IE6, likewise if you are using any IE below IE6 then test first
with IE6. Purely as IE6 is the one version I have tested to death on my
end with Xwiki..
I would suggest starting with the built in Error reporting (a small icon
in the bottom left of the explorer window), to determine if any errors
in script are the cause. It is better to activate the actual
notification for finding problems though.
To enable the IE script notification:
1) Go to the menu "Tools" => "Internet Options"
2) Select the "Advanced" tab
3) Under browsing, make sure the option "Display a notification about
every script error" is checked.
4) Perform Xwiki operations suspected of causing an error, to eliminate
script problems.
CSS problems rarely cause IE to crash, but it is also worth checking
that any custom CSS is compliant with IE (CSS1 and some special IE CSS
only, if I recall correctly - IE6 and below don't support CSS1 or CSS2).
Short of that, I would need more information such as a screenshot of the
crash screen (choose to view the data being sent, this provides the
modules that are crashing and can give some indication of where the
problem lies).
-----Original Message-----
From: THOMAS, BRIAN M (SBCSI) [mailto:bt0008@att.com]
Sent: 01 November 2006 16:05
To: xwiki-users(a)objectweb.org
Subject: [xwiki-users] IE browser crash
In a sane world, this would serve as just one more reason not to click
on the blue 'e'. In my world, however, it threatens to scuttle a
project to re-host an enterprise-wide reference web site, so I'm hoping
someone else has seen this. Considering how little I have to go on, I'm
embarassed to share it with the list, but I'm approaching desparation.
The evidence I have is sketchy, so the characterization is a bit thin,
but here goes:
On XWiki 0.9.840, IE occasionally crashes while reloading a document
after saving it. The save succeeds, and reloading the doc again causes
no problems. I don't yet have a handle on the browser's memory use or
anything characterizing the other docs the users have visited, but it
appears to be unrelated to the specific document. At the moment I'm not
aware of crashes at any other times, so I'm grateful for that much,
being the firmest bit of evidence I've got.
Anyone had any similar experiences that might shed light on the subject?
brain[sic]
8:03 p.m.
New subject: [xwiki-users] IE browser crash
Brandon:
Thanks for a quick response. I should have specified that it was IE6 (I
had all but forgotten that there was any other version).
And ditto on Firefox, though I use FireBug (and anything else I can get
my hands on - hadn't heard of "Web Developer"). After becoming used to
that, using IE is like working blindfolded, handcuffed, with thick
gloves on... in a sewer.
Your concern about sounding patronizing notwithstanding, you managed to
mention one thing I overlooked (looking at the error icon, duh) and one
thing of which I was unaware (option for notification on script errors)
as well one thing I've only just begun asking the users to do (sending
me the messages that Windows offers to send when tattling on a
misbehaving program).
Not bad on little to no evidence... if you're not careful, you might
encourage more of such questions in the future, to the everlasting
chagrin of all the regulars. I now submit to the discipline of the
group.
However, it's hard to imagine any (lawful) punishment that would deter
me from seeking help for a problem of this urgency, so perhaps you are
the one who should be punished...
brain[sic]
-----Original Message-----
From: Esbach, Brandon [mailto:Esbachb@tycoelectronics.com]
Sent: Wednesday, November 01, 2006 10:37 AM
To: xwiki-users(a)objectweb.org
Subject: RE: [xwiki-users] IE browser crash
IE can be a real nasty piece of work when it's not treated
right, and often even when it is.
I usually use firefox and the 3rd party extension called "Web
Developer" as this provides a page tester which tests even
CSS errors (among other very useful tools for general web development)
However, as you're talking IE, I still have some suggestions
for you to start out with.
[note: the following may sound patronising and are fairly low
grade checks, easy to do and quick to rule out common issues]
First things first though, if you are using IE7 then I would
first test with IE6, likewise if you are using any IE below
IE6 then test first with IE6. Purely as IE6 is the one
version I have tested to death on my end with Xwiki..
I would suggest starting with the built in Error reporting (a
small icon in the bottom left of the explorer window), to
determine if any errors in script are the cause. It is
better to activate the actual notification for finding
problems though. To enable the IE script notification:
1) Go to the menu "Tools" => "Internet Options"
2) Select the "Advanced" tab
3) Under browsing, make sure the option "Display a
notification about every script error" is checked.
4) Perform Xwiki operations suspected of causing an error, to
eliminate script problems.
CSS problems rarely cause IE to crash, but it is also worth
checking that any custom CSS is compliant with IE (CSS1 and
some special IE CSS only, if I recall correctly - IE6 and
below don't support CSS1 or CSS2).
Short of that, I would need more information such as a
screenshot of the crash screen (choose to view the data being
sent, this provides the modules that are crashing and can
give some indication of where the problem lies).
-----Original Message-----
From: THOMAS, BRIAN M (SBCSI) [mailto:bt0008@att.com]
Sent: 01 November 2006 16:05
To: xwiki-users(a)objectweb.org
Subject: [xwiki-users] IE browser crash
In a sane world, this would serve as just one more reason not
to click on the blue 'e'. In my world, however, it threatens
to scuttle a project to re-host an enterprise-wide reference
web site, so I'm hoping someone else has seen this.
Considering how little I have to go on, I'm embarassed to
share it with the list, but I'm approaching desparation.
The evidence I have is sketchy, so the characterization is a
bit thin, but here goes:
On XWiki 0.9.840, IE occasionally crashes while reloading a
document after saving it. The save succeeds, and reloading
the doc again causes no problems. I don't yet have a handle
on the browser's memory use or anything characterizing the
other docs the users have visited, but it appears to be
unrelated to the specific document. At the moment I'm not
aware of crashes at any other times, so I'm grateful for that
much, being the firmest bit of evidence I've got.
Anyone had any similar experiences that might shed light on
the subject?
brain[sic]
2 Nov
2 Nov
10:11 p.m.
New subject: [xwiki-users] IE browser crash
Well, I've been doing all that, and it doesn't seem that any Javascript
errors are triggering the crashes; very few of the XWiki pages elicit
errors of that sort from IE. I'm going to leave it on anyway, in case
they're cumulatively leading to some memory or stack corruption that is
later triggered by some otherwise harmless event.
But it occurs to me that if you've beaten XWiki against IE6 for a while,
you may have some clues about what kinds of things tip its equilibrium?
I'm grasping at straws here, as you can imagine. The perverse irony of
this situation is that the flaws of one Microsoft product may prompt
ditching XWiki in favor of another Redmond tar-baby: SharePoint Server.
brain[sic]
-----Original Message-----
From: THOMAS, BRIAN M (SBCSI)
Sent: Wednesday, November 01, 2006 1:03 PM
To: xwiki-users(a)objectweb.org
Subject: RE: [xwiki-users] IE browser crash
Brandon:
Thanks for a quick response. I should have specified that it
was IE6 (I had all but forgotten that there was any other version).
And ditto on Firefox, though I use FireBug (and anything else
I can get my hands on - hadn't heard of "Web Developer").
After becoming used to that, using IE is like working
blindfolded, handcuffed, with thick gloves on... in a sewer.
Your concern about sounding patronizing notwithstanding, you
managed to mention one thing I overlooked (looking at the
error icon, duh) and one thing of which I was unaware (option
for notification on script errors) as well one thing I've
only just begun asking the users to do (sending me the
messages that Windows offers to send when tattling on a
misbehaving program).
Not bad on little to no evidence... if you're not careful,
you might encourage more of such questions in the future, to
the everlasting chagrin of all the regulars. I now submit to
the discipline of the group.
However, it's hard to imagine any (lawful) punishment that
would deter me from seeking help for a problem of this
urgency, so perhaps you are the one who should be punished...
brain[sic]
1 Nov
1 Nov
11:14 p.m.
New subject: [xwiki-users] IE browser crash
On following your advice, I immediately got a very helpful alert saying
(roughly, from memory):
Line: 1
Char: 1
Object required
So now it begins. The first script tag included XWiki's skins.js, but I
don't see anything there that would provoke such a complaint. My guess
is that it would be caused by a reference to an attribute on an
undefined object. More than that, it didn't show on another document,
so on we go...
brain[sic]
3 Nov
3 Nov
9:54 a.m.
New subject: [xwiki-users] IE browser crash
This actually gives more to look at than you might realise at first..
It points at a script problem being the likely culprit.
Quick question: do you have the fancy tabs (from the Xwiki admin
section) setup?
-----Original Message-----
From: THOMAS, BRIAN M (SBCSI) [mailto:bt0008@att.com]
Sent: 01 November 2006 22:15
To: xwiki-users(a)objectweb.org
Subject: RE: [xwiki-users] IE browser crash
On following your advice, I immediately got a very helpful alert saying
(roughly, from memory):
Line: 1
Char: 1
Object required
So now it begins. The first script tag included XWiki's skins.js, but I
don't see anything there that would provoke such a complaint. My guess
is that it would be caused by a reference to an attribute on an
undefined object. More than that, it didn't show on another document,
so on we go...
brain[sic]
4:04 p.m.
New subject: [xwiki-users] IE browser crash
Interestingly enough, now that I have turned off the XML prolog, that
page no longer evokes that error dialog. Before you get too excited,
though, the identical page on another wiki also doesn't. The
differences are in the content (it's the Main.AllDocs page) and the
skin. Both are fitted with an enhancement that I added, which is a
SELECT menu of all the spaces, which has an onchange script that does a
window.scrollTo to the anchor created by the Heading-1-1 tag for that
space.
And, in answer to a question in your (later) reply, I do apparently have
the script debugger installed, though if I had remembered to answer that
question in my reply I would have said no. But only just now, when I
attempted to run a bookmarklet to enlarge a textarea on the
Doc.XWikiSyntax page (which doesn't have a textarea, but the {code}
macro box was too tiny to read), did I get a prompt asking me if I
wanted to debug the script. When I pushed the "yes" button, there it
was. Duh...
Que veut-dire "fancy tabs"? Is this an 0.9.840 feature, or is it
introduced in a later version?
brain[sic]
-----Original Message-----
From: Esbach, Brandon [mailto:Esbachb@tycoelectronics.com]
Sent: Friday, November 03, 2006 2:54 AM
To: xwiki-users(a)objectweb.org
Subject: RE: [xwiki-users] IE browser crash
This actually gives more to look at than you might realise at
first.. It points at a script problem being the likely culprit.
Quick question: do you have the fancy tabs (from the Xwiki admin
section) setup?
-----Original Message-----
From: THOMAS, BRIAN M (SBCSI) [mailto:bt0008@att.com]
Sent: 01 November 2006 22:15
To: xwiki-users(a)objectweb.org
Subject: RE: [xwiki-users] IE browser crash
On following your advice, I immediately got a very helpful
alert saying (roughly, from memory):
Line: 1
Char: 1
Object required
So now it begins. The first script tag included XWiki's
skins.js, but I don't see anything there that would provoke
such a complaint. My guess is that it would be caused by a
reference to an attribute on an undefined object. More than
that, it didn't show on another document, so on we go...
brain[sic]
6580
days inactive
6582
days old
6 comments
2 participants
participants (2)
-
Esbach, Brandon -
THOMAS, BRIAN M (SBCSI)