in reply to Re^3: ithreads memory leak
in thread ithreads memory leak
Ah I see this caveat noted in the thread docs now, thank you for clearing this up.
I'm happy to listen to any suggestions you can offer (when you have free time of course!), and I'm willing to put work into this, assuming it's near my level of competence.
Again, thanks!
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^5: ithreads memory leak
by BrowserUk (Patriarch) on Apr 09, 2015 at 19:00 UTC | |
I said 3 suggestion, but one of them was too complicated to merit discussion. If you choose option 1 and need further help, yell and I'll try to modify a copy of your code and post it, but I'm not going to waste the effort if you choose option 2 :) With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked
| [reply] [d/l] [select] |
by DNAb (Novice) on Apr 09, 2015 at 20:45 UTC | |
I've looked over both examples and while the second certainly looks easier, I agree that creating and destroying threads constantly is a waste compared to just starting two workers and sending them work. I mostly get where you are going with this, but the one thing that I can't visualize is how are we going to disregard the open timer if the user closes the showcase? The work has already been passed to the thread. Also the walk timer needs to respect multiple key presses and update the expiry time, and cease termination and "restart" work. | [reply] |
by BrowserUk (Patriarch) on Apr 09, 2015 at 21:20 UTC | |
I can't visualize is how are we going to disregard the open timer if the user closes the showcase? The work has already been passed to the thread. Also the walk timer needs to respect multiple key presses and update the expiry time, and cease termination and "restart" work. Then we need to be able to ask the thread to do two things: And that means adding a test : if( exists $showcase{ $showcasenum } ) { for an showcase number; And keeping a record of where the current timer for that showcase is: %showcase. Now, when 'add'ing a showcase, we remove any existing timer before adding a new one. And if the cmd eq 'del', then we just remove the existing timer.
Does that make sense? Does it cover all the bases? With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked
| [reply] [d/l] [select] |
by DNAb (Novice) on Apr 09, 2015 at 22:24 UTC |