Loading old/pre-populated profiles leads to freezing PM/crashing instance in ZP

[morpheus93]

I created many profiles with the profile creator and feeder from Santorini https://zennolab.com/discussion/threads/sozdanie-i-progrevanie-profilej-nagulivanie-kuki-dlja-dalnejshix-registracij.70865/ used an older version of ZP (7.1.2.0). Unfortunately it writes in the profile/browserprofiledata.zpdata invalid settings like

"screen":{"availLeft":50505,"availTop":50505,"availHeight":50505,"availWidth":50505,"left":50505,"top":50505,"height":50505,"width":50505,"pixelDepth":50505,"colorDepth":50505,..."

When I reload those profiles in the lastest version (7.2.1.0) it leads to freezing of PM and also to crashing ZP. Also if I'm able to load such a profile after several tries when I re-save it the invalid settings remain in the newly saved profile (browserprofiledata.zpdata).

What way would you recommend to handle such "invalid" profiles?

 

[VladZen]

What browser engine and browser profile emulation parameters were set in old profile when you created it?
Try to set the same in new version and load old profile.

 

[morpheus93]

What browser engine and browser profile emulation parameters were set in old profile when you created it?
Try to set the same in new version and load old profile.

I set Chrome engine and 100% Chrome (latest version) with 100% Desktop and Windows while creating the profiles in ZP 7.1.2.0.
Now I'm using the same settings in v 7.2.1.0 but from time to time it stucks or let the instance crash...

 

[VladZen]

I set Chrome engine and 100% Chrome (latest version) with 100% Desktop and Windows while creating the profiles in ZP 7.1.2.0.
Now I'm using the same settings in v 7.2.1.0 but from time to time it stucks or let the instance crash...

Try to open this profile as archive and remove localstorage and indexed db from there.
Then load updated profile into new version.

 

[morpheus93]

@VladZen Okay, Thank you for your appreciated help. I will try it that way.