Closed Bug 1469207 Opened 6 years ago Closed 6 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | dom/canvas/test/webgl-conf/generated/test_conformance__glsl__implicit__multiply_int_mat2.vert.html | application timed out after 370 seconds with no output when Gecko 62 merges to Beta on 18-06-2018

Categories

(Core :: Graphics: CanvasWebGL, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1472415
Tracking Status
thunderbird_esr52 --- unaffected
thunderbird_esr60 --- unaffected
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox60 --- unaffected
firefox61 --- unaffected
firefox62 - affected

People

(Reporter: apavel, Unassigned)

References

Details

(Keywords: intermittent-failure)

[Tracking Requested - why for this release]: Central as beta simulation: Treeherder link: Failure log: 04:37:22 INFO - TEST-START | dom/canvas/test/webgl-conf/generated/test_conformance__glsl__implicit__multiply_int_mat2.vert.html 04:37:22 INFO - GECKO(756) | JavaScript error: , line 0: uncaught exception: out of memory 04:37:22 INFO - GECKO(756) | JavaScript error: http://mochi.test:8888/tests/dom/canvas/test/webgl-conf/mochi-single.html?checkout/conformance/glsl/implicit/multiply_int_mat2.vert.html, line 38: TypeError: parent.SimpleTest is undefined 04:43:32 INFO - Buffered messages finished 04:43:32 ERROR - TEST-UNEXPECTED-TIMEOUT | dom/canvas/test/webgl-conf/generated/test_conformance__glsl__implicit__multiply_int_mat2.vert.html | application timed out after 370 seconds with no output 04:43:32 ERROR - Force-terminating active process(es). 04:43:32 INFO - Determining child pids from psutil... 04:43:32 INFO - [760, 762, 761] 04:43:32 INFO - ==> process 756 launched child process 760 04:43:32 INFO - ==> process 756 launched child process 761 04:43:32 INFO - ==> process 756 launched child process 762 04:43:32 INFO - Found child pids: set([760, 761, 762]) 04:43:32 INFO - Killing process: 760 04:43:32 INFO - TEST-INFO | started process screencapture 04:43:32 INFO - TEST-INFO | screencapture: exit 0 04:43:32 INFO - Killing process: 761 04:43:32 INFO - Not taking screenshot here: see the one that was previously logged 04:43:32 INFO - Killing process: 762 04:43:32 INFO - Not taking screenshot here: see the one that was previously logged 04:43:32 INFO - psutil found pid 761 dead 04:43:32 INFO - psutil found pid 760 dead 04:43:32 INFO - psutil found pid 762 dead 04:43:32 INFO - Killing process: 756 04:43:32 INFO - Not taking screenshot here: see the one that was previously logged 04:43:32 INFO - psutil found pid 756 dead 04:43:32 WARNING - runtests.py | Failed to get app exit code - running/crashed? 04:43:32 INFO - TEST-INFO | Main app process: exit 0 04:43:32 INFO - runtests.py | Application ran for: 0:07:56.083107 04:43:32 INFO - zombiecheck | Reading PID log: /var/folders/wh/8l3t57c95fb4p5qxbmr_y80r00000w/T/tmphBTzsMpidlog 04:43:32 INFO - ==> process 756 launched child process 760 04:43:32 INFO - ==> process 756 launched child process 761 04:43:32 INFO - ==> process 756 launched child process 762 04:43:32 INFO - zombiecheck | Checking for orphan process with PID: 760 04:43:32 INFO - zombiecheck | Checking for orphan process with PID: 761 04:43:32 INFO - zombiecheck | Checking for orphan process with PID: 762 04:43:32 INFO - mozcrash Downloading symbols from: https://queue.taskcluster.net/v1/task/Nq5E4NIxSOyRqZMwazmsyQ/artifacts/public/build/target.crashreporter-symbols.zip 04:43:45 INFO - mozcrash Copy/paste: /Users/cltbld/tasks/task_1529235167/build/macosx64-minidump_stackwalk /var/folders/wh/8l3t57c95fb4p5qxbmr_y80r00000w/T/tmp6oYv0y.mozrunner/minidumps/11501F0C-F4C6-4730-9551-09442BCCEC3F.dmp /var/folders/wh/8l3t57c95fb4p5qxbmr_y80r00000w/T/tmpinW70A 04:43:58 INFO - mozcrash Saved minidump as /Users/cltbld/tasks/task_1529235167/build/blobber_upload_dir/11501F0C-F4C6-4730-9551-09442BCCEC3F.dmp 04:43:58 INFO - mozcrash Saved app info as /Users/cltbld/tasks/task_1529235167/build/blobber_upload_dir/11501F0C-F4C6-4730-9551-09442BCCEC3F.extra 04:43:58 INFO - PROCESS-CRASH | Main app process exited normally | application crashed [@ libsystem_kernel.dylib + 0x114de] 04:43:58 INFO - Crash dump filename: /var/folders/wh/8l3t57c95fb4p5qxbmr_y80r00000w/T/tmp6oYv0y.mozrunner/minidumps/11501F0C-F4C6-4730-9551-09442BCCEC3F.dmp 04:43:58 INFO - Operating system: Mac OS X 04:43:58 INFO - 10.10.5 14F27 04:43:58 INFO - CPU: amd64 04:43:58 INFO - family 6 model 69 stepping 1 04:43:58 INFO - 4 CPUs 04:43:58 INFO - 04:43:58 INFO - GPU: UNKNOWN 04:43:58 INFO - 04:43:58 INFO - Crash reason: EXC_SOFTWARE / SIGABRT 04:43:58 INFO - Crash address: 0x7fff8ae434de 04:43:58 INFO - Process uptime: 476 seconds 04:43:58 INFO - 04:43:58 INFO - Thread 0 (crashed) 04:43:58 INFO - 0 libsystem_kernel.dylib + 0x114de 04:43:58 INFO - rax = 0x000000000100001f rdx = 0x0000000000000000 04:43:58 INFO - rcx = 0x00007fff597b7148 rbx = 0x0000000000001388 04:43:58 INFO - rsi = 0x0000000000000102 rdi = 0x00007fff597b71d0 04:43:58 INFO - rbp = 0x00007fff597b7190 rsp = 0x00007fff597b7148 04:43:58 INFO - r8 = 0x000000000000c3cb r9 = 0x0000000000001388 04:43:58 INFO - r10 = 0x000000000000041c r11 = 0x0000000000000202 04:43:58 INFO - r12 = 0x000000000000041c r13 = 0x0000000000000000 04:43:58 INFO - r14 = 0x00007fff597b71d0 r15 = 0x000000000000c3cb 04:43:58 INFO - rip = 0x00007fff8ae434de 04:43:58 INFO - Found by: given as instruction pointer in context 04:43:58 INFO - 1 libsystem_kernel.dylib + 0x1064f 04:43:58 INFO - rbp = 0x00007fff597b7190 rsp = 0x00007fff597b7150 04:43:58 INFO - rip = 0x00007fff8ae4264f 04:43:58 INFO - Found by: stack scanning 04:43:58 INFO - 2 libsystem_kernel.dylib + 0x14ea9 04:43:58 INFO - rbp = 0x00007fff597b7190 rsp = 0x00007fff597b7160 04:43:58 INFO - rip = 0x00007fff8ae46ea9 04:43:58 INFO - Found by: stack scanning 04:43:58 INFO - 3 XUL!google_breakpad::ReceivePort::WaitForMessage(google_breakpad::MachReceiveMessage*, unsigned int) [MachIPC.mm:7d593e4769ed90916840dfa6679b2c4e43268844 : 249 + 0x18] 04:43:58 INFO - rsp = 0x00007fff597b71a0 rip = 0x00000001099ec3ac 04:43:58 INFO - Found by: stack scanning 04:43:58 INFO - 4 XUL!google_breakpad::CrashGenerationClient::RequestDumpForException(int, int, int, unsigned int) [crash_generation_client.cc:7d593e4769ed90916840dfa6679b2c4e43268844 : 67 + 0xd] 04:43:58 INFO - rsp = 0x00007fff597b71b0 rip = 0x00000001099e2924 04:43:58 INFO - Found by: call frame info 04:43:58 INFO - 04:43:58 INFO - Thread 1 04:43:58 INFO - 0 libsystem_kernel.dylib + 0x17232 04:43:58 INFO - rax = 0x0000000002000171 rdx = 0x0000000000000001 04:43:58 INFO - rcx = 0x000000010c4885b8 rbx = 0x0000000000000000 04:43:58 INFO - rsi = 0x00007fff77551730 rdi = 0x0000000000000004 04:43:58 INFO - rbp = 0x000000010c488640 rsp = 0x000000010c4885b8 04:43:58 INFO - r8 = 0x0000000000000001 r9 = 0x0000000000000000 04:43:58 INFO - r10 = 0x000000010c4885d0 r11 = 0x0000000000000246 04:43:58 INFO - r12 = 0x00007fff94850258 r13 = 0x00007fff77550ec0 04:43:58 INFO - r14 = 0x000000010c4885d0 r15 = 0x000000010c488600 04:43:58 INFO - rip = 0x00007fff8ae49232 04:43:58 INFO - Found by: given as instruction pointer in context 04:43:58 INFO - 1 libdispatch.dylib + 0x4a6a 04:43:58 INFO - rbp = 0x000000010c488e50 rsp = 0x000000010c488650 04:43:58 INFO - rip = 0x00007fff94830a6a 04:43:58 INFO - Found by: previous frame's frame pointer
From talking with Ryan, I don't think we need to track intermittent failures from beta simulations. Other than asking Jeff to have a look, there's not a lot I can do here since it's not something where we can find a regression range. Aryx, what do you think?
Flags: needinfo?(aryx.bugmail)
Yes, no need to track intermittent failures unless they are very frequent.
Flags: needinfo?(aryx.bugmail)
:jgilbert there seem to be rather many such failures (on the integration trees), gl jobs with timeout and crash after with this signature: [@ libsystem_kernel.dylib + 0xsth]: bug 1469272, bug 1468373, bug 1468479, bug 1469202, bug 1469111 etc. Do we keep filing new bugs for these failures or should we make a general one for all of them? Thank you.
Flags: needinfo?(jgilbert)
(In reply to Andreea Pavel [:apavel] from comment #3) > :jgilbert there seem to be rather many such failures (on the integration > trees), gl jobs with timeout and crash after with this signature: [@ > libsystem_kernel.dylib + 0xsth]: bug 1469272, bug 1468373, bug 1468479, bug > 1469202, bug 1469111 etc. > > Do we keep filing new bugs for these failures or should we make a general > one for all of them? > > Thank you. General bug. Hopefully we can get more of a handle on these with the splitting of mochitest-gl in bug 1471112.
Flags: needinfo?(jgilbert)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.