Closed Bug 593385 Opened 9 years ago Closed 9 years ago

TEST-UNEXPECTED-FAIL | /tests/editor/libeditor/text/tests/test_bug569988.html | application timed out after 330 seconds with no output

Categories

(Core :: Editor, defect)

x86
Windows Server 2003
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mats, Unassigned)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file, 1 obsolete file)

TEST-UNEXPECTED-FAIL | /tests/editor/libeditor/text/tests/test_bug569988.html | application timed out after 330 seconds with no output

WINNT 5.2 mozilla-central debug test mochitests-3/5 on 2010/09/03 06:37:01
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1283521021.1283526651.25874.gz
See also bug 569988 comment 21 and 22.
The prompt was loaded but was never focused. Then, what should I do? Should I print a todo message and quit in such case?
Blocks: 438871
How about adding a timeout function in onPromptLoad to run after 5 seconds, and do an ok(false, "input not focused"), close the window and finish the test.  You should also clear the timeout if onPromptFocus was successfully called.

It might also make sense to wrap the contents of the onPromptLoad in a try/catch block and report any exceptions in case something weird is throwing there...
(In reply to comment #3)
> How about adding a timeout function in onPromptLoad to run after 5 seconds, and
> do an ok(false, "input not focused"), close the window and finish the test.

It creates anther orange...
(In reply to comment #4)
> (In reply to comment #3)
> > How about adding a timeout function in onPromptLoad to run after 5 seconds, and
> > do an ok(false, "input not focused"), close the window and finish the test.
> 
> It creates anther orange...

Sure, but it's better than aborting the rest of the test suite, isn't it?  My suggestion will be useful to try to determine why the test is failing in the first place as well.
Attached patch Patch v1.0 (obsolete) — Splinter Review
Ugh, we met a bug of javascript engine.

When this patch calls clearTimer(), then, quitting the function without any warnings/errors.
Comment on attachment 472368 [details] [diff] [review]
Patch v1.0

Oh, I see what I mistook. Sorry for the spam.

# But I'm not sure why the code doesn't put any messages to the error console.
Attachment #472368 - Attachment is obsolete: true
Attachment #472368 - Flags: review-
Attached patch Patch v2.0Splinter Review
This doesn't succeed in doing timeout...

> ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property!: 'Error', file m:/mozilla-a/src/js/src/xpconnect/src/xpcwrappednativescope.cpp, line 792
> xul!XPCWrappedNativeScope::FindInJSObjectScope+0x00000000000000FB (m:\mozilla-a\src\js\src\xpconnect\src\xpcwrappednativescope.cpp, line 847)
> xul!XPCWrappedNativeScope::FindInJSObjectScope+0x0000000000000022 (m:\mozilla-a\src\js\src\xpconnect\src\xpcprivate.h, line 1470)
> xul!xpc_CloneJSFunction+0x0000000000000070 (m:\mozilla-a\src\js\src\xpconnect\src\xpcwrappednativeinfo.cpp, line 63)
> xul!XPCNativeMember::NewFunctionObject+0x000000000000009B (m:\mozilla-a\src\js\src\xpconnect\src\xpcwrappednativeinfo.cpp, line 125)
> xul!DefinePropertyIfFound+0x000000000000078E (m:\mozilla-a\src\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 458)
> xul!XPC_WN_ModsAllowed_Proto_Resolve+0x0000000000000158 (m:\mozilla-a\src\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1883)
> xul!CallResolveOp+0x00000000000003E2 (m:\mozilla-a\src\js\src\jsobj.cpp, line 4396)
> xul!js_LookupPropertyWithFlags+0x00000000000000D5 (m:\mozilla-a\src\js\src\jsobj.cpp, line 4439)
> xul!js_LookupProperty+0x0000000000000026 (m:\mozilla-a\src\js\src\jsobj.cpp, line 4274)
> xul!JSObject::lookupProperty+0x0000000000000042 (m:\mozilla-a\src\js\src\jsobj.h, line 715)
> xul!LookupPropertyById+0x00000000000000AE (m:\mozilla-a\src\js\src\jsapi.cpp, line 3067)
> xul!GetPropertyDescriptorById+0x0000000000000023 (m:\mozilla-a\src\js\src\jsapi.cpp, line 3497)
> xul!JS_GetPropertyDescriptorById+0x0000000000000027 (m:\mozilla-a\src\js\src\jsapi.cpp, line 3547)
> xul!nsOuterWindowSH::NewResolve+0x00000000000000F8 (m:\mozilla-a\src\dom\base\nsdomclassinfo.cpp, line 6594)
> xul!XPC_WN_Helper_NewResolve+0x0000000000000316 (m:\mozilla-a\src\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1191)
> xul!CallResolveOp+0x0000000000000172 (m:\mozilla-a\src\js\src\jsobj.cpp, line 4347)
> xul!js_LookupPropertyWithFlags+0x00000000000000D5 (m:\mozilla-a\src\js\src\jsobj.cpp, line 4439)
> xul!js_GetPropertyHelper+0x000000000000007E (m:\mozilla-a\src\js\src\jsobj.cpp, line 4779)
> xul!js_GetMethod+0x000000000000007A (m:\mozilla-a\src\js\src\jsobj.cpp, line 4876)
> xul!js::Interpret+0x000000000000B792 (m:\mozilla-a\src\js\src\jsinterp.cpp, line 4112)
> xul!js::InvokeCommon<int (__cdecl*)(JSContext *,JSObject *,unsigned int,js::Value *,js::Value *)>+0x00000000000004F2 (m:\mozilla-a\src\js\src\jsinterp.cpp, line 577)
> xul!js::Invoke+0x00000000000002A1 (m:\mozilla-a\src\js\src\jsinterp.cpp, line 696)
> xul!js::InternalInvoke+0x00000000000000AC (m:\mozilla-a\src\js\src\jsinterp.cpp, line 736)
> xul!js::InternalCall+0x0000000000000032 (m:\mozilla-a\src\js\src\jsinterp.h, line 651)
> xul!JS_CallFunctionValue+0x00000000000000B3 (m:\mozilla-a\src\js\src\jsapi.cpp, line 4874)
> xul!nsJSContext::CallEventHandler+0x0000000000000403 (m:\mozilla-a\src\dom\base\nsjsenvironment.cpp, line 2174)
> xul!nsGlobalWindow::RunTimeout+0x00000000000006A8 (m:\mozilla-a\src\dom\base\nsglobalwindow.cpp, line 8580)
> xul!nsGlobalWindow::RunPendingTimeoutsRecursive+0x000000000000003A (m:\mozilla-a\src\dom\base\nsglobalwindow.cpp, line 5856)
> xul!nsPendingTimeoutRunner::Run+0x0000000000000020 (m:\mozilla-a\src\dom\base\nsglobalwindow.cpp, line 5900)
> xul!nsThread::ProcessNextEvent+0x00000000000001FA (m:\mozilla-a\src\xpcom\threads\nsthread.cpp, line 547)
> xul!NS_ProcessNextEvent_P+0x0000000000000053 (m:\mozilla-a\firefox-debug-build\xpcom\build\nsthreadutils.cpp, line 250)
> xul!mozilla::ipc::MessagePump::Run+0x00000000000000FD (m:\mozilla-a\src\ipc\glue\messagepump.cpp, line 110)
> xul!MessageLoop::RunInternal+0x0000000000000056 (m:\mozilla-a\src\ipc\chromium\src\base\message_loop.cc, line 220)
> xul!MessageLoop::RunHandler+0x0000000000000082 (m:\mozilla-a\src\ipc\chromium\src\base\message_loop.cc, line 203)
> xul!MessageLoop::Run+0x0000000000000043 (m:\mozilla-a\src\ipc\chromium\src\base\message_loop.cc, line 177)
> xul!nsBaseAppShell::Run+0x0000000000000050 (m:\mozilla-a\src\widget\src\xpwidgets\nsbaseappshell.cpp, line 186)
> xul!nsAppShell::Run+0x0000000000000042 (m:\mozilla-a\src\widget\src\windows\nsappshell.cpp, line 243)
> xul!nsAppStartup::Run+0x000000000000006A (m:\mozilla-a\src\toolkit\components\startup\src\nsappstartup.cpp, line 191)
> xul!XRE_main+0x0000000000--DOMWINDOW == 14 (0B666F70) [serial = 13] [outer = 0AD37C68] [url = http://mochi.test:8888/tests/editor/libeditor/text/tests]
> 002C5E (m:\mozilla-a\src\toolkit\xre\nsapprunner.cpp, line 3665)
> firefox!NS_internal_main+0x00000000000002B2 (m:\mozilla-a\src\browser\app\nsbrowserapp.cpp, line 158)
> firefox!wmain+0x000000000000011E (m:\mozilla-a\src\toolkit\xre\nswindowswmain.cpp, line 120)
> firefox!__tmainCRTStartup+0x00000000000001A8 (f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c, line 583)
> firefox!wmainCRTStartup+0x000000000000000F (f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c, line 403)
> kernel32!BaseThreadInitThunk+0x0000000000000012
> ntdll!RtlInitializeExceptionChain+0x0000000000000063
> ntdll!RtlInitializeExceptionChain+0x0000000000000036
Oh, the assertion is put after closing the dialog. So, is the timer blocked by the modal dialog??
I think you should be using gPromptWindow.setTimeout and gPromptWindow.clearTimeout.
(In reply to comment #10)
> I think you should be using gPromptWindow.setTimeout and
> gPromptWindow.clearTimeout.

No, it doesn't work.
(In reply to comment #12)
> (In reply to comment #10)
> > I think you should be using gPromptWindow.setTimeout and
> > gPromptWindow.clearTimeout.
> 
> No, it doesn't work.

In what sense?
Has only happened twice.  => WFM.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.