Share:
Notifications
Clear all

June 24 2026 APP 2.0.0-beta46 has been released !

Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.

May 27 2026 APP 2.0.0-beta45 has been released !

Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

[Solved] MEMORY TO FILE MAPPER: still trying to remove mapped file

4 Posts
2 Users
0 Reactions
1,010 Views
(@lilacwatcher)
Brown Dwarf
Joined: 2 years ago
Posts: 3
Topic starter  

I have twice had APP fail to complete its integration workflow, and instead repeatedly give me the message 'MEMORY TO FILE MAPPER: still trying to remove mapped file'. 
On the most recent occasion, with 1590 lights, reduced to 1210 because some didn't Register, about 80megapixels. There should have been no filespace problem: APP said that it required about 1.6Tb to integrate, using a drive with over 3Tb available.

Any advice would be welcome.



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5363
 

Hi Stephen @lilacwatcher,

Thank you very much for posting your issue.

APP should not have this issue on a regular internal diskdrive. Is the drive internal and always mounted?

If it is an external drive, then I suspect your issue can occur if the Operating System or other software on your computer tries to unmount the drive for some reason, then APP can no longer remove the temporary file I think causing the warning message.

Can you tell me what kind of harddisk that you are using and if it is a permanently mounted drive or perhaps and external drive that you connect on occasion?

I have opened an issue on our list to investigate this further and fix this issue.

Mabula

 



   
ReplyQuote
(@lilacwatcher)
Brown Dwarf
Joined: 2 years ago
Posts: 3
Topic starter  

Merci beaucoup d'avoir repondu si rapidement.

My SSD has been connected to my Windows 11 laptop through a Thunderbolt docking station. Prompted by your suggestion that the problem lay with the connection to my drive, I instead connected the SSD directly to my laptop, i.e. not through the Thunderbolt. This time, the processing proceeded smoothly, with no problems: 1590 lights were successfully stacked, and I am very pleased with the result.

Thank you for taking time to help me with this issue.

 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5363
 

Hi Stephen @lilacwatcher,

That is really great, thank you very much for the feedback ! I am happy to read that all is okay now.

If an external drive disconnects unexpectedly, the integration will break down/can't finish and APP can not remove that temporary file. I have added an extra warning now in the console panel that states: MEMORY TO FILE MAPPER: !!! maybe the harddisk was disconnected or unmounted unexpectedly?

That will hopefully indicate to other APP users what happened and what caused the issue.

Mabula



   
ReplyQuote
Share: