Rank: Advanced Member
Groups: Guest
Joined: 3/3/2008(UTC)
Posts: 185
Thanks: 8 times
|
Hi, we are already using the latest version of Aurigma DLL.
But, after we do a lot of works by using the component, then it might come out with this error. Even in the code, I already placed a lot of system.gc.collect
5 - Unable to commit memory.(Aurigma.GraphicsMill)
Please advice.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 6/22/2008(UTC)
Posts: 27
|
You'll need to give more info.
What component are you using, (i'm assuming it's the MLV from your other posts).
When you say lots of work, what does that mean?
What sort of files are you using?
What format is the target bitmap in?
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 3/3/2008(UTC)
Posts: 185
Thanks: 8 times
|
Yes, we are using MLV
Lot sa works means that, we will be adding like 10 ImageVObject to the MLV (with like 200dpi), Remove them, a lot of iteration of adding and removing...
And after the designer work on a lot of those iteration without closing the application, and they might be able to hit this error....
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 6/22/2008(UTC)
Posts: 27
|
Sounds like we're developing similar apps, I'm actually about to step into some beta testing around this issue myself, I'll post back here if I run into any similar issues.
How are you adding images to the MLV? By using the CreateDesigner function?
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 3/3/2008(UTC)
Posts: 185
Thanks: 8 times
|
Yes....
Adding object by using the CreateDesigner or direct adding Vobject to it.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 6/22/2008(UTC)
Posts: 27
|
Ok I've seen some weird memory problems now, not sure what's causing them, but one of my beta testers reported the MLV turning into a big red X, (looks like Graphics Memory is having a problem), when the MLV control is changing size.
I haven't managed as yet to get a procedure to replicate the problem, it's looking a bit random at the moment.
I'm about to bring more beta testers on board, so hopefully that will shed some common factors on this.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 1/31/2005(UTC)
Posts: 458
Was thanked: 5 time(s) in 5 post(s)
|
Hi Ching Yen, Could you send us a small demo with description how to reproduce the issue? By the way, have you tried memory-friendly approach of VObjects usage described in this article: How to Overlay Images? |
|
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 3/3/2008(UTC)
Posts: 185
Thanks: 8 times
|
Hi,
I think the issue is random and it only appear when it's run out of memory... As we do have beta tester with 1MB RAM and 2MB RAM, and it shows that, the chances for the 1MB RAM hit the error is higher. But, as long as they close the program which should be clearing the stack, then, it will not reproduce the error code after the program restart.
My best guess on the trigger for the error is using MLV adding and delete VObjects (like adding 10 objects and remove 10 objects and keep repeat the same steps with different photo - high res, 300dpi)...until you think u in total added 1000 vobjects, and removed 1000 vobjects....i guess if you continue to do the adding and removing, you should be able to hit that error reported....... (or u may write a scrip just to add image vobject and remove it)...
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 1/31/2005(UTC)
Posts: 458
Was thanked: 5 time(s) in 5 post(s)
|
Hi Ching Yen, Please, could you provide us with more detailed information about the issue? The best case - it is demo application with steps to reproduce the problem. Or, the very-very detailed report of the used actions and features, sizes and formats of the images (not only DPI) and exception details (it would be great to have stack traces). Something like: 1) Load JPEG image NxP pixels and 300 dpi with ScaleToActualSize = true. 2) Remove it and dispose the correspondingVObject & bitmap. 3) Call System.GC.Collect(); 4) Repeat actions 1 - 3 for 3000 cycles - in 5 launches from 10 I got "OutOfMemoryException with such stack trace: <... stack trace goes here ...>. Edited by user Monday, July 28, 2008 9:48:02 PM(UTC)
| Reason: Not specified |
|
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.