To GGG and anyone with the "Unable to MapViewOfFile" errors

Ok so there seems to be quite a lot of people getting this error and i myself having had this error, have been quite annoyed with it, to say the least. So i looked around the forums and there seems to be pieces of information here and there and decided to share what seems to be the current status of the error and some fixes that have been suggested and tested.

So this error itself shows up as something like:

"Unable to MapViewOfFile in MapChunk. Error Code: 8 Offset: 1005387776 Size: 2791085594" or
"Unable to MapViewOfFile in MapChunk. Error Code: 2138570752 Size: 1462501"

What and when does this happen?

This seems to occur mostly in Act 3 of the open beta but has been confirmed to happen in Act 2 of open beta, though nowhere near as frequently. The "Dark Forest" map in particular seems to have a lot of problems for people in Act 2, with me also experiencing this once in this map. As far as im concerned, it has never shown up in the closed beta before so it seems to be something to do with the open beta.

In addition, this error occurs mostly when people are changing maps, such as walking from one map into another or tping back to town or another map. The error has also shown up while not changing maps, although the frequency of this happening is much much less than the changing of maps.

When the error occurs, an exception window will open behind the game and display the error, which is usually followed by some kind of Java error notification or Microsoft Visual C++ Runtime Library error notification. The game then crashes and closes.

Upon some testing, it seems that even if the game crashes, the last map that you were in may still have not reset, with all the monsters dead and map revealed up to where you have been.

Some suggested fixes to the problem.

-The first and most common fix that has been suggested is that this error only shows up in the 32bit version of windows and not the 64bit version. In this sense, you can install a 64bit version of windows on your computer and this crash should no longer occur.

This has been confirmed by a number of people on the forum who have switched from 32bit to 64bit versions of windows on the same computer with the error subsequently going away. However, there has also been a minority of people who have said that they have switched to the 64bit version and still encounter this error, although that number is significantly less than those that have confirmed that the error does stop.

-The second fix that has been suggest by "AMonkeyTrick" is that if you start the game with the sound disabled, you also stop encountering this error. This is achieved by " right clicking the shortcut to the game, going to properties, and in the target section, change it to "C:\Program Files\Grinding Gear Games\Path of Exile\Client.exe" --nosound".

At least two people in that thread have confirmed that this does work although one has said that they still encounter this error. I have personally tried this and although it still crashed for me, the crash happened only once during an entire day's playing, which i was pretty happy with after the 20-30 min crashing that occurred before.

It also appears that you may have to change your graphics settings to normal for this to work.


So thats pretty much all i have now. If anyone would like to add anything or correct me on anything, feel free to do so.

Please find an official way to fix this GGG, this is a great game and i would hate to have it so unfairly tarnished by such an error.

It has something to do with the way the open beta handles memory usage.

They actualy managed to break it. Never had this error in closed beta. now constantly have it and its even killed me on hardcore wich in turn made me quit playing completely.

I have asked plenty times for a fix.

Apparently the way the game handles memory usage on 32 bit is broken. and anything you can do that lowers your memory usage helps.

I hope they can fix this soon so its worth trying to play again without dying.

See here http://www.pathofexile.com/forum/view-thread/108634

Short version
The reason for this error (and related errors) is because the game requires a certain amount of data to describe the world to be retained in memory at any given point, the amount of which is roughly related to the complexity of the area you are in. However a problem occurs when the game is unable to retain this data due to a limitation of 32-bit Windows which governs how much data can be accessed at a time.

Long version
Insufficient address space to address the required amount of game data. The reason the issue manifests itself on 32-bit builds is due to the address space partitioning scheme (ie., 2GB userland, 2GB kernel). The developers have marked the image as /LARGEADDRESSAWARE thus why the problem does not occur under WOW64 on 64-bit builds.

The impetus of the problem however remains a fault of the devs; relying exclusively on the heap which becomes extremely fragmented (both internal and external). Analyzing the request stream shows clear patterns in allocation behavior that could be exploited easily (~40% of allocations are just for a dword or so). There's also extreme lock contention amoungst a few worker threads and, after some analysis with VTune, shows about 80% of time is spent on either synchronous processing or waiting on other threads (it would've been better to single thread this entire program to avoid the ctx switch overhead)

It was suggested that I re-download the game from another ISP since mine was sending a corrupt file. I did so and the problem remains. Reducing quality does lower the frequency of the error, but it doesn't solve it.

Now the only solution is to upgrade to 64 bit, but I've tried that and my cpu can't support it.

Sucks to be me! Hopefully the next major patch or so will deal with this on the dev end and I won't have to buy a new computer just to play this game.

Until then I guess I'll be getting 24 characters through acts 1 and 2 -____-

"

It was suggested that I re-download the game from another ISP since mine was sending a corrupt file. I did so and the problem remains. Reducing quality does lower the frequency of the error, but it doesn't solve it.

Now the only solution is to upgrade to 64 bit, but I've tried that and my cpu can't support it.

Sucks to be me! Hopefully the next major patch or so will deal with this on the dev end and I won't have to buy a new computer just to play this game.

Until then I guess I'll be getting 24 characters through acts 1 and 2 -____-

See here http://www.pathofexile.com/forum/view-thread/108634