Out of memory crash when opening a Sisulizer project - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

Support forum of the software localization tool Sisulizer

.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Not logged in - Login | Register

.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Out of memory crash when opening a Sisulizer project

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

Printer Friendly

Out of memory crash when opening a Sisulizer project - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

Author

Post

Posted: Tue Mar 27th, 2012 12:45 pm

jorjam
Member

Joined:	Tue Mar 27th, 2012
Location:
Posts:	4
Status:	Offline

I just upgraded to build 330 from build 329 and tried opening my Sisulizer project. It took a long time and then I got an "Out of memory" error. See attachment.

I also tried to install a clean installation of Sisulizer and also restarted my machine just in case - with no luck. Same problem.

I am now not able to use Sisulizer build 330. Please help!

Attachment: Sisulizer - out of memory.png (Downloaded 47 times)

Posted: Tue Mar 27th, 2012 02:22 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	2988
Status:	Offline

Hello,

I've two questions:
1. Could you tell me when this project stopped work (e.g. after updated to latest build, after adding new sources to project, etc.)?
2. Could you upload to us your SLP file (packed as zip archive) via private Upload feature?
BTW:
Here is article about our upload system: http://www.the-localization-tool.com/?p=808

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Tue Mar 27th, 2012 02:24 pm

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Monschau, Germany
Posts:	2207
Status:	Offline

Remember you can always return to some older build:

http://www.sisulizer.com/support/versionarchive.shtml

Would be nice to verify if it still works in 329.

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Wed Mar 28th, 2012 12:20 pm

jorjam
Member

Joined:	Tue Mar 27th, 2012
Location:
Posts:	4
Status:	Offline

Thanks for the quick replies!

I now noticed that I actually upgraded my client from build 328 to 330 and not from 329.

1. I upgraded my client and then tried to open my project. While waiting for it to open, the error message appeared.

2. I will upload the slp file right now.

Like Markus suggested, I reinstalled the build 328 and was able to open my project again and to work with it.

Posted: Wed Mar 28th, 2012 01:22 pm

jorjam
Member

Joined:	Tue Mar 27th, 2012
Location:
Posts:	4
Status:	Offline

New info:

Now I got the same error when opening the project with build 428. However, the client still opened up and I am able to use the file open option and open the project and start working with translations.

Posted: Wed Mar 28th, 2012 03:33 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	2988
Status:	Offline

Hello,

Thank you for file. Your project is really very big (137 MB) and I can't open it on my machine both in 330 and 328. Sisulizer is Delphi 32-bit application and can't address more than 2 GB RAM. I'll forward it to our developers.
I've following advices:

You can split project into smaller parts.
Binary resources e.g. pictures could use lot of memory. So if your project contains many unnecessary binary resources you could exclude it from SLP. Here is our article on blog related to this issue: http://www.the-localization-tool.com/?p=266

However, I hope our developer will find a better solution for you.

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Apr 2nd, 2012 07:44 am

Ilkka.Salmenius
Administrator

Joined:	Wed Aug 8th, 2007
Location:	Tokyo, Japan
Posts:	1316
Status:	Offline

Your project is too large. The current Sisulizer is 32 bit application and cannot use more than 2.8 GB memory. You have to split you project into smaller projects.

Ilkka

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Apr 16th, 2012 01:06 pm

jorjam
Member

Joined:	Tue Mar 27th, 2012
Location:
Posts:	4
Status:	Offline

Hello and thank you for your feedback.

Although it is not the perfect solution, we will look into if we can split or maybe exclude binary resources.

Thanks again.

Posted: Tue Apr 17th, 2012 01:05 pm

Alepet
Member

Joined:	Tue Apr 17th, 2012
Location:
Posts:	4
Status:	Offline

Hello.
I am a colleague of jorjam. We are trying to fix this problem, and unfortunately I can't find out how I can split or remove unwanted resources from project without actually opening it. And as we know it's impossible even for your developers.
Do you have any solutions?

Posted: Wed Apr 18th, 2012 06:08 am

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	2988
Status:	Offline

Alepet wrote: And as we know it's impossible even for your developers.
Do you have any solutions?
We can open your SLP in external tools, so we'll preview it and try find potential solutions.

Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Wed Apr 18th, 2012 06:46 am

Alepet
Member

Joined:	Tue Apr 17th, 2012
Location:
Posts:	4
Status:	Offline

Thank you very much! Looking forward to see the solution.

Posted: Wed Apr 18th, 2012 07:40 am

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	2988
Status:	Offline

Hello,

Your SLP contains 6 SLN sources and you could use following solution:
Create 2 copies of your SLP. Open 1th copy in external editor and remove 1-3 source nodes (SLP use plain XML format) for 1-3 sln files. Check syntax and save file. Open 2nd copy in external editor and remove 4-6 source nodes for 4-6 sln files. Check syntax and save file.
It should split your SLP to 2 parts. Let me know if this works for you.

Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Fri Apr 20th, 2012 08:35 am

Alepet
Member

Joined:	Tue Apr 17th, 2012
Location:
Posts:	4
Status:	Offline

Thank you for advice. I will try it today and inform you next week.
Have a nice weekend.

Posted: Mon Apr 23rd, 2012 01:04 pm

Alepet
Member

Joined:	Tue Apr 17th, 2012
Location:
Posts:	4
Status:	Offline

Hello. Your advise helped us to solve the issue. Splitting by sources worked fine.

Thank you very much.

Posted: Mon Apr 23rd, 2012 01:56 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	2988
Status:	Offline

Hello,

I'm glad it works for you. Sorry for inconvenience, but this is limitation of programming platform, not direct limitation of Sisulizer, so we can't fix this in easy way.

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Current time is 03:32 pm
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Out of memory crash when opening a Sisulizer project

WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize