Menu
▾
▴
#222 Opening Multiple instances of Ultradefrag causes all windows to stop responding
my computer has alot of hard drives and frequently i will have multiple instances of ultradefrag running at the same time. as of 7.0.0 opening a second instance of ultradefrag will cause both windows to stop responding. the problem is so bad i had to roll back to my previous version
Should probibally clarify that All Windows referes to all instances of ultradefrag not all currently running applications
Thank you for your report. It looks like the latest stable release of wxWidgets isn't stable enough, so we have to wait for an update. As soon as it will be available I'll recompile UltraDefrag using it.
I can't fix the bug right now as I cannot reproduce it on my testing machines. On the other hand, the previous stable UltraDefrag v6 release doesn't depend on wxWidgets library, so can be safely used instead till the bug will be fixed.
Here are my system specs incase it's due to a hardware issue
though the only thing i have that could cause an issue with ultradefrag would be the Sil3132 external sata card i use for my hotswap bay
if it is as you say an issue with this specific library perhaps you could include a check box in the controller function to use the standard windows UI from the previous version during install
Last edit: Mike loeven 2016-03-20
As soon as I'll find a bit of time I'll recompile the program with wxWidgets 3.1.0 released recently. Hope that will fix some bugs.
The latest 7.0.1 release has been compiled using the most recent wxWidgets 3.1.0 library which fixes a lot of bugs. I'm not sure whether it fixes the reported issue or not, so just give it a try and reopen the ticket if nothing has been changed.
Tested the new version and something is still causing the UI to lock up when more than one instance of the program is running.
as you have been unable to reproduce the issue i have also attached a video demonstrating the issue
Do you know if there are any log files i could send you or some method of taking a memory dump when the issue occurs ?
Last edit: Mike loeven 2016-03-26
Found a very interesting behavior.
If you make a copy of the ultra defrag directory and run one from program files and the second instance from the portable directory they will both function normally.
running two instances from the same directory will result in the UI Locking up
So if i want to run say 4 instances of ultradefrag i would need to make 4 copies of the application directory.
Last edit: Mike loeven 2016-03-26
Thank you very much for addtional information. Logging can be done using Debug View program. I'll check sources once again, but at the moment I just can't imagine why it might hang, especially taking into account the fact that it doesn't being launched from different directories.
My guess at this point is perhaps the two instances are trying to write to a single file and confusing each other with the inconsistant changes ?
I think i figured out the issue. I ran Debug view and as soon as i opened the second window i was spamed with errors saying that ultradefrag was unable to delete it's log file. I suspect that there is no method of failing gracefully or generaiting a second log file if the current log file is locked
Last edit: Mike loeven 2016-05-13
Thank you for additional information. I'll run more tests and try to adjust the code to get rid of the problem or, at least, generate more useful debugging output. It's just a matter of time, as soon as I'll get some progress, I'll let you know.
Have the exact same problem here :(
Full System Info report is attached.
Basic System Specs Below:
Dell Inspiron 13-5368 Signature Edition
Processor: Intel Core i5-6200 CPU @ 2.3GHz + 2.4GHz
RAM: 8GB
System Type: 64-bit (of course)
OS: Windows 10 Home x64
Build Number: Version 10.0.14393 Build 14393
Last edit: Jeb Eldridge 2016-11-24
Thank you for feedback. Let's hope some day we'll make the program more reliable.
Issue seems to still be present as of 7.0.2 any idea of when the 7.0.3 milestone will be out ?
Last edit: Mike loeven 2017-04-06
Since the issue is still open it is not fixed yet.
The problem is fixed only if the issue is closed.
Stefan
Thank you, guys, for keeping records of what has to be done yet. As soon as I'll be able to return back to the project, sure, I'll try my best to fix all the bugs you have reported. It's just a matter of time, sooner or later, I believe, I'll be back as it was very enjoyable for me in the past to work on the project.
The issue - for me - happens only sometimes in 7.0.2 for Windows 10 x64. I feel as if the program has stabilized out a bit, but as said, it's still happening sometimes.