Ruakij
/
ManagedPool
1
0
Fork 0
Code Issues 2 Pull Requests Projects Releases 1 Wiki Activity

Labels Milestones

New Issue

Because of no lifetime, extra spawned objects are directly destroyed afterwards #3

Open
opened 6 years ago by Ruakij · 0 comments
Ruakij commented 6 years ago (Migrated from gitea.railduction.eu)

Since there is no set lifetime for an extra spawned object (if more objects are spawned),
it is directly destroyed because there is no use.

There needs to be a lifetime, so the spawned object can be used again and the system can adapt to the current usage.

Since there is no set lifetime for an extra spawned object (if more objects are spawned), it is directly destroyed because there is no use. There needs to be a lifetime, so the spawned object can be used again and the system can adapt to the current usage.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
v1.1
v1.1.0
Labels
Apply labels
Clear labels   
bug

Something is not working   
Critical

Critical   
duplicate

This issue or pull request already exists   
enhancement

New feature   
help wanted

Need some help   
invalid

Something is wrong   
question

More information is needed   
todo

This is todo   
wontfix

This won't be fixed
No Label
bug
Critical
duplicate
enhancement
help wanted
invalid
question
todo
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Set Project
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Ruakij/ManagedPool#3
Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(<nil>)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes