MantisBT - MEGA
View Issue Details
0000217MEGAMain Formpublic2016-07-13 21:062016-07-13 21:06
guest 
 
normalminorhave not tried
newopen 
PCWindows10
MEGA 11 (Graphical Interface version) 
 
Satoshi
Aoki
aoki@ns.bg.s.u-tokyo.ac.jp
aoki@ns.bg.s.u-tokyo.ac.jp
0000217: Error during ML tree bootstrapping
I don't know the "Category" I chose is correct, but please let me report an error I encountered.

Memory Deficit Error has occurred during ML tree bootstrapping on MEGA7 (ver. 7. 0. 18).
Just after the error, the OS has freezed.
The same dataset was safely processed with MEGA6 (ver. 6. 06).

Also, the processing time with MEGA6 seemed shorter than that of MEGA7, although I expected the opposite (since it's a 64 bit version software).
Memory leaking?

Thank you for your attention and this software (for free!).
I hope MEGA will be a better software.
The other software which was running when the error has occurred:
CPU Temperature Monitor (http://www.cputhermometer.com/ [^])

The processed data set: 33OTU, 306bp.
----------------------------ML tree inferring settings---------------------------
Bootstrap:1000
Substitution: Nucleotide
Model: Kimura 2-parameter model
Rate among Sites: Gamma Distributed (10)
Gaps: Complete Deletion
Inferring option: (SPR level5), (Default NJ/BioNJ)
Branch Swap Filter: Very Weak
Number of Threads: 4
--------------------------------System Information-------------------------------
Processor: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz (4 CPUs), 0000048:0000003.2GHz
Memory: 8192MB RAM
Available OS Memory: 8130MB RAM
No tags attached.
jpg Mega3 bug.jpg (58,116) 1969-12-31 17:33
https://megasoftware.net/mantis_bt/
jpg IMGP4484.JPG (964,083) 2016-07-13 21:06
https://megasoftware.net/mantis_bt/
Issue History
2016-07-13 21:06guestNew Issue
2016-07-13 21:06guestFile Added: IMGP4484.JPG

Notes
(0000145)
gstecher   
1969-12-31 17:33   
I asked the user to supply the datafile or a more detailed account of the steps required to produce the error.
(0000176)
gstecher   
1969-12-31 17:33   
This is the same problem as #221. It seems to happen at random on XP machines. Perhaps SP2 has fixed this. Need to do more testing.