プロジェクト

全般

プロフィール

Vote #73887

完了

Ruby hangs when adding a subtask

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
72
issue_org_id:
14015
author_id:
61511
assigned_to_id:
1
comments:
12
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
71
ステータス-->[Closed]

説明

We experience serious problems since updating from V2.3.0 => V2.3.1:

When adding a subtask, this process can take up to 3 minutes, where ruby produces 99% system load.

A similar effect can be seen, if adding 'related issues', ths takes up to 1 minute.

This bug might be related to the fixes for #13586

or to the current bug #13654

The defect currently makes our Redmine impossible to work with.

Does anybody see similar effects with V2.3.1?

Ralf


journals

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I've looked into it and suspect that this is a problem with the method @all_dependent_issues@ in @issue.rb@, Line 857. It uses a lot of recursive calls and can probably be simplified.
--------------------------------------------------------------------------------
A patch for this issue is appended, based on revision 11811. It contains a much faster implementation of @all_dependent_issues@ and some additional tests for the method. The new implementation sometimes returns different results, but as far as I can jugde it, that happens due to bugs in the old implementation.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Patch committed, thanks for your work.
--------------------------------------------------------------------------------
Hi,

i patched my redmine 2.3.1 with latest issue.rb http://www.redmine.org/projects/redmine/repository/revisions/11833/entry/trunk/app/models/issue.rb, now i am able to set a parent issue again (#13654) but now the icons are not corretly displayed for all subissues, see screenshot
--------------------------------------------------------------------------------
some more details, see screenshot, issue 6293 was created with 2.3.1 without patch. Patch installed, issues 6295-8 were created without relation. Then i set parent_id to 6294: Icons are missing.
--------------------------------------------------------------------------------
forget my notes about missing icons. Now i've learned that icons are only displayed if the parent issue is above the issue. So if i sort on 'parent id' my parent issue is the first and all my sub issues are displayed with icons :-)
--------------------------------------------------------------------------------
Merged in 2.3-stable, thanks for the feedback.
--------------------------------------------------------------------------------
Huge thanks guys. We just upgraded our 1.4.4 install to 2.3.1 and were running into 100% CPU / RAM / swap usage, DB transaction locks, and what looked like infinite loop situations. This looks to have resolved it.
--------------------------------------------------------------------------------
I'm facing this problem.

I've upgraded to 2.3.2 but the problem persists:
# When I'm setting a child issue using the parent_issue_id on a issue that has some related issues I receive 'Parent task is invalid'

Thanks
--------------------------------------------------------------------------------


related_issues

relates,Closed,13654,Can't set parent issue when issue relations among child issues are present
relates,Closed,13914,Circular dependency issue when issue dependency is set

Admin Redmine さんが約4年前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョン2.3.2_72 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0