Closed
Bug 1319103
Opened 8 years ago
Closed 8 years ago
unrelated bugs getting added to dependency graph
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: dylan)
Details
Attachments
(1 file)
I've been using the Dependency Graph for the past month or so to get a view of the project tracked by bug 1278974. Specifically, https://bugzilla.mozilla.org/showdependencygraph.cgi?id=1278974&display=tree&rankdir=TB. Everything was working fine for awhile, but today I'm starting to see unrelated bugs sometimes show up in the graph. Sometimes it's a handful, sometimes it's hundreds. Here's a few examples: https://people-mozilla.org/~bhearsum/sattap/5a5967c6.png (what it should look like) https://people-mozilla.org/~bhearsum/sattap/57f71947.png (a massive number of extras) https://people-mozilla.org/~bhearsum/sattap/ebb08e3f.png (a handful of extras) Until about 10 days ago, none of the bugs in the graph were resolved, so that's something that's changed recently, but I'm not sure it's related at all.
Updated•8 years ago
|
Assignee: dependency.views → nobody
Component: Dependency Views → General
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Assignee | ||
Comment 1•8 years ago
|
||
Note: This will only manifest under mod_perl. Several variables were declared with our(), which means they are global. As a side effect, they're not cleared out between requests. This was never noticed before because usage of dependendcygraph is smallish, and prior to my initial memory leak work the webheads didn't live very long.
Assignee: nobody → dylan
Attachment #8812867 -
Flags: review?(dkl)
Comment 2•8 years ago
|
||
Comment on attachment 8812867 [details] [review] Pull Request r=dkl
Attachment #8812867 -
Flags: review?(dkl) → review+
Assignee | ||
Comment 3•8 years ago
|
||
To git@github.com:mozilla-bteam/bmo.git 6b551fb..78eac22 master -> master
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•