Ruleset.CreateIcon is inefficient in ruleset usages
See original GitHub issueIt came to my attention that some rulesets are using sprites for their icons, creating a new TextureStore
every call to CreateIcon()
. This is super inefficient and may lead to memory exhaustion.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
About rulesets
Rulesets help you to control how people can interact with branches and tags in a repository.
Read more >Work with custom rulesets
Use the following workflow to deploy a custom ruleset at the account level: Create a custom ruleset. Add rules to your custom ruleset....
Read more >Customize a rule set - Visual Studio
Learn how to customize code analysis rule sets in Visual Studio. See how to create new sets from scratch or from existing sets....
Read more >Predefined ruleset and RuleApp properties
Name Valid values Default value Classic rule engine only
ilog.rules.engine.cacheRuleflowData true, false false Yes
ilog.rules.engine.hasherGeneration true, false false Yes
ilog.rules.engine.rete5Task true, false false Yes
Read more >Creating a ruleset and a ruleset version
For easier maintenance and development of your application, create rulesets so that you can categorize the rules that your application uses ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think you understand what you’re saying here. This doesn’t need open discussion; it’s an issue (causing potential crashes) purely at the
osu.Game
end and the comment above was more for myself than anyone else.Sure, I didn’t intend to say it was completely correct, rather than it just being “more proper” from a performance standpoint. I understand the namespacing implications.