Intermittent failure in jsreftest.html?test=js1_5/Regress/regress-404755.js | Unknown :0: uncaught exception: A possible leak is observed item 1

NEW
Unassigned

Status

()

defect
P3
normal
9 years ago
3 years ago

People

(Reporter: philor, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [test disabled])

Attachments

(1 obsolete attachment)

(Reporter)

Description

9 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1265403040.1265404941.31122.gz
Linux mozilla-central opt test jsreftest on 2010/02/05 12:50:40
s: moz2-linux-slave16

REFTEST INFO | Loading file:///builds/moz2_slave/mozilla-central-linux-opt-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-404755.js
begin test: js1_5/Regress/regress-404755.js
BUGNUMBER: 404755
STATUS: Do not consume heap when deleting property
66 9
 FAILED! [reported from test()] uncaught exception: A possible leak is observed
REFTEST TEST-UNEXPECTED-FAIL | file:///builds/moz2_slave/mozilla-central-linux-opt-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-404755.js | Unknown :0: uncaught exception: A possible leak is observed item 1

Comment 1

9 years ago
are we timing the GC here? let's not do that.
(Reporter)

Comment 2

9 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1265423110.1265423642.23083.gz
WINNT 5.2 mozilla-central opt test jsreftest on 2010/02/05 18:25:10
s: win32-slave35
REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-opt-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-404755.js | Unknown :0: uncaught exception: A possible leak is observed item 1

Comment 3

9 years ago
(In reply to comment #1)
> are we timing the GC here? let's not do that.

The test indeed times the GC. Often it is the only possibility to have a leak detector. Before the introduction of the background sweep the test was reliable.  It could be made reliable again if we add possible debug-only function to wait for the background GC to complete. Alternatively we can add a flag to js_GC not to do background sweeping and use that in the test.

Comment 4

9 years ago
We should be disabling tests like this that rely on timing. These tests are always flaky. I'm going to mark this as random until we have a better way.

Comment 5

9 years ago
Posted patch mark the test as random (obsolete) — Splinter Review
It's not ok to leave these turning the tinderbox orange.

Updated

9 years ago
Attachment #425706 - Attachment is patch: true
Attachment #425706 - Attachment mime type: application/octet-stream → text/plain

Comment 6

9 years ago
igor fixed this a different way in bug 530157. we'll use that instead.

Updated

9 years ago
Attachment #425706 - Attachment is obsolete: true

Updated

9 years ago
Whiteboard: [orange] → [orange][test disabled]

Updated

9 years ago
Blocks: 404755
Whiteboard: [orange][test disabled] → [test disabled]
Assignee: general → nobody

Comment 7

3 years ago
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.