• 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

Crashes at least once per use

But still: Windows resource manager shows that RW is using approximately 400-500 MB of the main memory when the exception occurs, leaving several GB of free memory. So the image size and number of tabs should not make a difference even if it is a 32 bit application.

Windows often lies about stuff like that. :( Especially when .Net is involved, what the Task Manager shows you is not necessary accurate. All of the out-of-memory crash reports include exact diagnostics of these details, and I think the smallest one showed about 1.4GB of memory allocations when the crash occurred. That total does NOT include the program itself, nor some of the other resources it's utilizing, all of which must fit into slightly less than 2GB of space.

And the other mystery remains: at startup after the crash RW comes up with exactly the same number of tabs and images open. The only difference is that the offending action that led to the exception now runs smoothly.

That strongly implies memory fragmentation. When you start the product anew, all the fragmentation that occurred during the previous run is reset. So the problem doesn't arise after the restart, but it would very likely occur after further use of the product for some amount of time, during which memory fragmentation would again arise.
 
This certainly isn't an out-of-memory bug. This MIGHT be an issue with the name indexing engine, but I have no idea what might be going on. The only way to sort out an indexing issue would be to actually receive your database. We capture "playback" information for the name index within the database. We can pull that out and see if we can recreate the problem that way, which would allow us to locate and fix the issue. Of course, this assumes the issue IS with the indexing engine and not something else.

Please provide us with your database. Attach download information for the database to a support ticket concerning these crashes. And please include as much detail about the steps you're taking within RW that are resulting in the crash.

Please also give us a step-by-step sequence from a point after you've performed a re-index, including the names involved. If this is not an issue with the indexing engine, your step-by-step details will be critical to us figuring out what is going wrong with the linking mechanism.

Thanks!

I will do it later this week. I am busy next few evenings and won't have the time to give you the detail to make it useful.

My database is approaching 600MB so will need info returned to me from ticket for uploading it.
 
I will do it later this week. I am busy next few evenings and won't have the time to give you the detail to make it useful.

My database is approaching 600MB so will need info returned to me from ticket for uploading it.

When you're ready, details on how to get us your database will be found in the following thread, which is stickied at the top of the forums if you should need it again in the future:
http://forums.wolflair.com/showthread.php?t=48663

Thanks!
 
So, this conversation has spurred a question for me. I have a system that is chalked full of tables in the game manual. Typically, I find it easier to take a screen snippet of the table and load it as a simple pic in RW. Is this a bad practice? From a memory / realm size stand point am I creating problems that will surface down the road? I think the answer is no, but I thought it was worth asking.
 
I do it a lot as well, especially for map legends that share multiple maps. I will snippet it and add as picture below the maps.

Large complex tables that will take more effort to remake than worth it, I do the same as you meek.

Time vs reward vs efficiency vs value = my work.

Snip tool is my bestest friend.
 
When you're ready, details on how to get us your database will be found in the following thread, which is stickied at the top of the forums if you should need it again in the future:
http://forums.wolflair.com/showthread.php?t=48663

Thanks!

Submitted report, received case #.
Its long and details the link crash issue and a few minor issues I have observed. I mention it in the case, but to give you a heads up, the most recent heavy work was done in "T1-4 Temple of Elemental Evil" during my QA pass work, so maybe focusing there will help. The Realm "Return to the Elemental Evil" is new and so far not a single crash I remember, but I am not doing much manual linking yet, but I have seen examples of all my minor issues reported.

All realms that have more then just my initial frame work (you will know what I mean when you look) have seen the link/crash issue to some degree. But some of them have not seen recent QA work where I see most of the crashes. "I6 Ravenloft" is new, but I have not yet done any QA, the text paste was less than stellar and I have not yet come to terms with the work to be done, so though new, not really a good candidate for linking issues I have seen, but feel free to have fun in them all!

As per thread I have emailed David for an alternative method to email for my database. even zipped it will not attach to an email.

I am leaving for a funeral so please allow for a few days to get it to you.
 
So, this conversation has spurred a question for me. I have a system that is chalked full of tables in the game manual. Typically, I find it easier to take a screen snippet of the table and load it as a simple pic in RW. Is this a bad practice? From a memory / realm size stand point am I creating problems that will surface down the road? I think the answer is no, but I thought it was worth asking.

Unless the tables are scanned at overly high resolution, this should be perfectly fine. I assume the table are effectively at around 100dpi, which is appropriate for on-screen viewing. That's not a problem. And you're handling them as picture snippets - not smart images - within the topics, right? If so, then you should be fine on that count as well.

The two big issues are very high resolution for extensive zooming combined with smart images (which entail lots of layers to manage all the aspects). Neither of those are applicable here.
 
Or OneDrive, or GoogleDrive, or whatever "free" service you happen to like using... :)

Free?>"Free"? hehe

I never even considered using my 365 account's Onedrive. But arrived back far to late last night so I just uploaded it, and just shared it via email to David this morning. I live in the sticks so I only have crappy 5/1 service, took serious time to upload an almost 450MB file.

I have more storage in the cloud then I have on my local NAS.
 
Back
Top