[Archivesspace_Users_Group] white screen lock-out

Tang, Lydia ltang5 at mail.lib.msu.edu
Wed Mar 30 10:07:21 EDT 2016

Hi Chris and everyone,

I wouldn’t be trying to save more then 10 lines at once (referring to my earlier post about the ease of losing RDE data – which BTW has gotten better, maybe I’m getting the hang of it or maybe there was a tweak on the back end, but I haven’t lost my data nearly as often as the fall), but the white screen lock-out happens even when I erase an archival object.  It happens on a regular basis for me, where I either have to log back in to our Aspace instance or even have to switch to a new browser and try again.  I am using Google Chrome as the browser, but also use Safari if I have to.

My IT folks increased the uh – buffer (sorry, not techie) memory, but this lock-out still occurs.  When it does, their logs are not able to show the problem.

Thanks so much for any help you could provide!



Hi Lydia,

How many rows are you trying to save at once? And which browser? You might be killing your browser's javascript engine.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group> <archivesspace_users_group-bounces at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>> on behalf of Tang, Lydia <ltang5 at mail.lib.msu.edu<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>>
Sent: Tuesday, March 29, 2016 11:03 PM
To: archivesspace_users_group at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
Subject: [Archivesspace_Users_Group] white screen lock-out

Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out.  I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource.  I was just wondering if this is a local problem for me, or whether it is more widespread?  Thank you so much,

More information about the Archivesspace_Users_Group mailing list