Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

'out Of Memory' - Xplode 4.1

Featured Replies

I just can't seem to get away from the alpha. In 4.1 the "wait-problem" is fixed (kudos to you :)), but I have another one now.

After some time it runs out of memory. Installers complain about it and after 6 error messages or so XPlode just quits. Everything works fine with the alpha version.

I attached my error log, just ignore the 'file not found' errors, they are just results from typo's. :P

Tnx,


nanaki, try using a script to kill uneeded processes, somethings start or hang sometimes during setup, taking up memory, or try allocating more memory for your virtual machines :P

Would you mind checking if XPlode is taking up all the RAM?

Might've missed some memory allocations...

Add "Memory Usage" and "Virtual Memory Size" to the columns in the task manager, if they're not there already...

  • Author

Holy crap, it's definitly XPlode. :/

Alright, I tried collecting as much information as possible.

First thing's first, I can't go using Task Manager as I'm installing during T-12 stage. :) But I used pslist to log every step. I created a "lite" XPlode script to test it out a bit. After every install I logged the memory usage. XPlode.exe keeps on growing and growing...

Included are the following:

- XPlode script

- XPlode log (btw, the version string is out-of-date ;))

- 1.txt (first log) and 11.txt (last log) fully

- 2.txt until 10.txt only Xplode.exe

Information about pslist logs:

Pri = Priority

Thd = Number of Threads

Hnd = Number of Handles

Priv = Private Virtual Memory

It goes from low in the first log (7MB) to a whopping 178MB in the last log.

One last thing worth mentioning, I think XPlode4a also does this, but in a lesser deal.

Hope this helps fix some stuff.

Ahh the problems with 2GB ram... you never see these things :P

Can I get you to remove certain items within the XML, to try and narrow down which item is causing this?

Yikes.

There's something fundamentally wrong. LIke, REALLY wrong. Massive allocations whenever a plugin is run... gonna be a pain figuring out where.

I'll look into it ASAP.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.