Hi,
One of our applications was exhibiting a bad allocation error when attempting a TTree::CloneTree(0) call on a relatively simple ntuple. It seems I can reproduce this interactively, using ROOT v5.18.00b. The file in question was generated with ROOT v5.16.00 and is the result of a filtering job. I am inquiring to find out more details of how this file was generated by one of our collaborators… however the file is available here:
ftp://ftp-glast.slac.stanford.edu/glast … merit.root
Interestingly, if I omit the t->GetEvent(0) line, the TTree::CloneTree(0) call succeeds. Am I triggering this behavior with my call to GetEvent without setting up any branch pointers? Or is that just coincidence?
-
*
-
W E L C O M E to R O O T *
-
*
- Version 5.18/00b 10 March 2008 *
-
*
- You are welcome to visit our Web site *
-
[root.cern.ch](http://root.cern.ch) *
-
*
ROOT 5.18/00b (branches/v5-18-00-patches@22563, Mar 28 2008, 13:51:00 on win32)
CINT/ROOT C/C++ Interpreter version 5.16.29, Jan 08, 2008
Type ? for help. Commands must be C++ statements.
Enclose multiple statements between { }.
root [0] TFile *f = new TFile(“Skimmer_merit.root”)
root [1] TTree t = (TTree)f->Get(“MeritTuple”)
root [2] t->GetEvent(0)
(Int_t)(2020)
root [3] TFile *outFile = new TFile(“test.root”,“RECREATE”)
root [4] TTree *t2 = t->CloneTree(0)
Fatal in TStorage::ReAllocChar: storage exhausted
aborting
==========================================
=============== STACKTRACE ===============
================ Thread 0 ================
ntdll!KiFastSystemCallRet()
kernel32!WaitForSingleObject()
libCore!TWinNTSystem::DispatchOneEvent()
================ Thread 1 ================
libCore!DefaultErrorHandler()
================ Thread 2 ================
ntdll!KiFastSystemCallRet()
kernel32!Sleep()
libCore!TWinNTSystem::TimerThread()
================ Thread 3 ================
ntdll!KiFastSystemCallRet()
libCore!`anonymous namespace’::GetProgramCounter()
0xffffffffff006aec ??
==========================================
============= END STACKTRACE =============
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application’s support team for more information.
Thanks,
Heather