• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Continuing frustration with crashes

K

kbs666

Well-known member
I use RW on 2 very capable desktop systems, an r7 1700, 16 GB RAM, a 1TB SSD and my home system is an R5 1600, 16 GB RAM, 240 GB SSD, !TB HDD. Both systems crash to the desktop frequently when ever I try to switch tabs while one of those tabs is a smart image that is 10 MB or larger.

I am fully aware that the problem is the 32 bit .NET that RW runs under. I am also aware that the last time this was discussed the problem was DevExpress controls used in RW did not come in a 64 bit flavor. Surely that situation has changed by now? Is there any chance that a migration to 64 bit will happen after the CM goes live?
 
kbs666 said:
I use RW on 2 very capable desktop systems, an r7 1700, 16 GB RAM, a 1TB SSD and my home system is an R5 1600, 16 GB RAM, 240 GB SSD, !TB HDD. Both systems crash to the desktop frequently when ever I try to switch tabs while one of those tabs is a smart image that is 10 MB or larger.
Click to expand...

A 10MB image doesn't really help to know the actual size of the image. Is it above approx. 3000x3000 pixels?
 
pixel count is irrelevant. A 10 MB PNG image could be significantly different scale than a gif or jpg or the same size.
 
kbs666 said:
pixel count is irrelevant. A 10 MB PNG image could be significantly different scale than a gif or jpg or the same size.
Click to expand...

Pixel size is exactly relevant. Whilst RW stores a PNG or GIF or JPG inside the database in that compressed format, as soon as you display it in a tab then it get stored in memory as a standard uncompressed multi-coloured picture. This uncompressed picture will always take up the same amount of memory for the same resolution image - so all 3000x3000 images will take up the same memory when displayed in a tab.

As you know, since you've been on the forums for a while, this is a known limitation which has various work-arounds.
 
I'm not interested in rehashing workarounds. I'm solely interested in finding out if the underlying problem is getting fixed in the near future.
 
You must log in or register to reply here.
Back
Top