When a process is rolled back as a result of deadlock the difficulty which arises is

When a process is rolled back due to a deadlock, several difficulties can arise:

1. Loss of Computation: The main difficulty is the loss of computation. The process might have altered some data from its original state before it entered the deadlock. Rolling back the process means losing all the computations and changes it made, which can be costly in terms of time and resources.

2. Starvation: If a process is repeatedly rolled back due to deadlocks, it may never get a chance to execute fully. This situation is known as starvation.

3. Resource Management: After rollback, the system needs to manage the resources that were previously held by the process. This can be complex, especially if resources were shared among multiple processes.

4. Determining Rollback Point: It can be difficult to determine how far to roll back a process. The system needs to ensure that rolling back to a certain point will indeed break the deadlock.

5. Overhead Costs: The process of rolling back itself can be expensive in terms of system overhead, as it involves context switching, memory management, and possibly re-loading data from disk.

6. Repeated Deadlocks: If the conditions that led to the deadlock are not addressed, the deadlock situation may occur again after the process is rolled back and resumed.