Viewing Bug Advanced Details
544 Doclib Addons feature always 10-13-05 08:05 02-03-06 11:38
gawarho  
meyers_tim  
normal  
closed  
open  
none  
none  
PrintId gets inconsistent results
When running a command/file based version of printId and a JNI called memory based version the results are not always the same.
Bug Notes
meyers_tim   
02-01-06 15:24   
We are also seeing this issue with dlResizeImage
meyers_tim   
02-03-06 11:38   
This appears to be an artifact of different versions of the Java Virtual Machine and how they interperate floating point numbers, and not a DOCLIB issue.




Viewing Bug Advanced Details
442 DLComponent feature always 05-18-05 08:14 02-01-06 12:04
amsakak  
amsakak  
normal  
closed  
open  
none  
none  
dlgetlines documentation
update documentation to include type of input expected and any conversions that are performed
Bug Notes
meyers_tim   
12-19-05 10:47   
Saki, can this bug be closed?
amsakak   
02-01-06 12:04   
Mission accomplished.




Viewing Bug Advanced Details
404 DLImage major always 03-17-05 16:49 12-19-05 09:47
gawarho  
meyers_tim  
normal  
closed  
open  
none  
none  
DLImage fails to allocate memory
This may actually be two problems in one:

First I have an image that I am trying to convert from Color to Black and White. It fails to work as DLImage runs out of memory (who knows why as it is one image) in dlAllocImageData(). Please see me at government site for the sample program and image file to recreate the problem.

Second because doclib does not appear to call set_new_handler() an exception of type std::bad_alloc is thrown -- thus any of the checks in the code to see if the new operator returned null are not used. Also the documentation about such exceptions coming from the STL should probably be noted.
Bug Notes
gawarho   
03-17-05 17:09   
I found the reason for the memory allocation error -- however getting the memory exception is still a surprise waiting to happen.
sdsampa   
03-18-05 09:16   
Glen, just for continuity, can you add a bugnote that describes the reason for the memory allocation error?
meyers_tim   
12-19-05 09:47   
I believe much, if not all, of this problem has been remedied due to the summer task to improve the robustness of DOCLIB. Previously, when such exceptions were not caught DOCLIB would seg fault fairly profusely, and much work has gone into fixing these issues.

Additionally, very large image sets have been run through DOCLIB and pushed through purify to help catch anymore memory related errors.

I think it is safe to close the bug, and any future issues can be dealt with on a case-by-case basis.